root / pykota / trunk / README @ 927

Revision 927, 10.5 kB (checked in by jalet, 21 years ago)

Groups quota work now !

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1# $Id$
2
3PyKota - Print Quota for CUPS
4
5(c) 2003 Jerome Alet <alet@librelogiciel.com>
6This program is free software; you can redistribute it and/or modify
7it under the terms of the GNU General Public License as published by
8the Free Software Foundation; either version 2 of the License, or
9(at your option) any later version.
10
11This program is distributed in the hope that it will be useful,
12but WITHOUT ANY WARRANTY; without even the implied warranty of
13MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
14GNU General Public License for more details.
15
16You should have received a copy of the GNU General Public License
17along with this program; if not, write to the Free Software
18Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
19
20====================================================================
21
22READ SPECIAL LICENSING AND REDISTRBUTION TERMS IN THE FILE 'LICENSE'
23
24====================================================================
25
26PyKota is a complete Print Quota system for the Common Unix Printing
27System (aka CUPS), which works by directly querying the printers
28for the number of pages they have printed.
29
30Actual working features :
31
32        - Per printer user and group quotas.
33       
34        - Automated email warning of users above quota to the
35          user himself and to the print quota administrator.
36       
37        - CUPS filter for quota accounting : pykota
38       
39        - Command line print quota editor : edpykota
40       
41        - Command line print quota report generator : repykota
42       
43        - Command line print quota automated warning sender : warnpykota
44       
45        - Command line tools mimic the disk quota utilities for
46          easier mastering.
47       
48        - Centralized storage of quotas : you can manage quotas for
49          different printers on different print servers and store them all
50          on the same quota storage server.
51          WARNING : actually all your printers must have an unique name,
52                    but this may change in a future version.
53                   
54        - SNMP querying of any networked SNMP-enabled printer.
55       
56        - Netatalk querying of any networked AppleTalk-enabled printer.
57       
58        - External command querying of any printer : you can use
59          you own querying command, e.g. to query a printer via
60          the serial port, sending it a special PJL job and
61          reading the result. See the example scripts in the
62          "untested" directory and try to adapt them to your
63          configuration.
64       
65        - Special scripts included for a seamless integration of
66          PyKota on Debian machines.
67         
68        - Complete job history is saved. This will allow more
69          complex reports in the future.
70         
71        - Price per page and price per job can be defined for 
72          every printer. A job's price is the sum of the
73          price per job for this printer plus the number of
74          pages multiplied by the price per page for this
75          printer.
76         
77        - User's account balance and lifetime paid money are now
78          stored in the Quota Storage, and account balance can be
79          used to limit the user printing instead of a print quota.
80          Actually you can limit either by account balance OR by
81          print quota, but maybe both should be checked at the
82          same time. Tell me what you prefer.
83         
84All the command line tools accept the -h | --help command line option
85which prints all the available options and show usage examples.
86       
87Planned features are described in the TODO file.
88
89Actually only the lazy quota method is implemented. What do I call
90lazy method ?
91
92  The lazy method consists in querying the printer (actually via SNMP
93  or Netatalk) for its total pages counter, just before the beginning
94  of a job, and use this to modify the *preceding* user's quota. So
95  you're always late of one print job, but this is generally ok,
96  especially because a check is also done to see if the current user
97  is allowed or not to print.
98 
99  Problem may theorically arise in batches of successive print jobs by
100  different users when there's no sleep time between two jobs : the
101  used pages may theorically be attributed to an incorrect user in the
102  case that the printer is asked for its page counter at the beginning
103  of a new job and before the end of the previous job. This depends on
104  the printer speed and time between jobs, but so far I've not seen
105  any problem with moderately used printers. This also depends on CUPS
106  internal behavior : if CUPS doesn't begin to send a job to a printer
107  before the previous one is completely printed, then there's no
108  problem.
109 
110  Other querying methods which won't suffer from this possible
111  problem, but probably from other ones ;-) will be implemented in the
112  future.
113 
114PyKota is known to work fine with HP Laserjet 2100 and 2200, and
115Apple LaserWriter 16/600 PS.
116
117It should also work fine with any printer capable of outputing
118its lifetime printed pages counter via either SNMP or AppleTalk.
119
120If your printers don't support SNMP or AppleTalk, then making them
121work with PyKota is up to you. Some sample scripts which can query
122non-SNMP printers for their lifetime page counter are included in
123the ./untested directory. You'll have to test and adapt them though,
124and define them as external requesters in the PyKota configuration
125file. See the sample configuration file to learn how to do that.
126
127============================================================
128
129INSTALLATION:
130=============
131
132WARNING :
133=========
134
135  If you run a PyKota version lower than 1.01, you definitely have to
136  upgrade you Quota Storage Database. Please read the documentation
137  included in the initscripts subdirectory first !
138 
139Prerequisite :
140--------------
141   
142  You need to have the following tools installed on the CUPS Server :
143 
144    - CUPS
145    - Python v2.1 or above
146    - eGenix' mxDateTime Python extension
147    - PostgreSQL's PygreSQL Python extension and the PostgreSQL client
148      libraries.
149    - SNMP tools (specifically the snmpget command) if you plan to
150      request your printer's lifetime page counter via SNMP.
151    - Netatalk (specifically the pap command) if you plan to
152      request your printer's lifetime page counter via AppleTalk.
153   
154  You need to have the following tools installed on the Quota Storage 
155  Server :
156 
157    - PostgreSQL
158   
159  PygreSQL and the PostgreSQL client libraries's versions on the CUPS
160  Server must match the PostgreSQL version used on the Quota Storage
161  Server.
162 
163  This list of prerequisite software may change in the future, when
164  PyKota will support more functionnalities you will be given
165  alternatives.
166 
167  Of course the CUPS Server and the Quota Storage Server can be the
168  very same machine if you've got a tiny network, or you can have
169  multiple CUPS Servers all storing their quotas on the same Quota
170  Storage Server if you've got a bigger network.
171 
172Then :   
173------
174 
175Download the latest PyKota version from the CVS tree on :
176
177    http://savannah.nongnu.org/projects/pykota
178
179Just type :
180
181    python setup.py install
182
183You may need to be logged in with sufficient privileges (e.g. root)
184
185The installation script will now automatically check if some software
186is missing and ask you if you still want to proceed with the
187installation or abort it completely.
188
189Go to the initscripts subdirectory of PyKota's sources, and choose
190the appropriate storage backend for your configuration. Read
191the associated README file and execute the initialization script
192to create an empty PyKota Storage. Upgrade scripts may be
193provided as well.
194
195Copy the conf/pykota.conf.sample sample configuration file to
196/etc/pykota.conf, and adapt this file to your own needs and
197configuration. The installation script tries to do this for
198you if needed and you agreed to this action.
199
200Modify the PPD files for each printer on which you want to manage
201print quotas, for example /etc/cups/ppd/lp.ppd :
202
203--- Add the line below exactly as-is somewhere near the top ---
204*cupsFilter:  "application/vnd.cups-postscript 0 /usr/bin/pykota"
205--- Add the line above exactly as-is somewhere near the top  ---
206
207Modify the path to the pykota executable if needed, unfortunately
208you have to supply the correct absolute path here due to CUPS
209internals, or put the pykota executable into /usr/lib/cups/filter
210instead of into /usr/bin.
211
212Do this for each ppd file present in this directory if you want
213to enable quota on every printer.
214         
215WARNING : In the case you've got a non-postscript printer, chances
216          are that the *cupsFilter is already filled-in and points
217          to cupsomatic or such a print filter. In this case please
218          check if you can switch your printer to PostScript mode
219          or if there's a way to make it accept PostScript jobs.
220          If yes then ensure that your workstations uses a PostScript
221          printer driver, and replace the *cupsFilter line with the
222          one pointing to the pykota filter. This should work, but
223          is currently untested.
224          If your printer really needs the original *cupsFilter line
225          then you may not be able to use PyKota easily for now.
226
227Add printers and users to the quota system and set their quota values :
228
229    $ edpykota --add -P printer -S softlimit -H hardlimit user1 ... userN
230       
231    launching edpykota without any argument or with the --help
232    command line option will show you all the possibilities.
233
234Restart CUPS, for example under Debian GNU/Linux systems :         
235
236    $ /etc/init.d/cupsys restart
237       
238Your users now should be able to print but not exceed their
239printing quota.
240
241To see printer command usage, you can use :
242
243    $ repykota --printer lp
244   
245or :
246
247    $ repykota
248   
249    which will print quota usage for all users on all printers,
250    along with totals.
251   
252SECURITY : You should ensure that only the print quota administrator
253           can run the warnpykota command, but this is actually not
254           enforced in the program. Any user able to launch warnpykota
255           could flood over-quota users' email boxes.
256           
257           You should ensure that only the print quota administrator
258           can run the edpykota command, but this is actually not
259           enforced in the program. Otherwise, any user could modify
260           his/her or other people's print quota.
261         
262           launching : chmod 750 /usr/bin/warnpykota /usr/bin/edpykota
263           should make you reasonably safe.
264           
265============================================================
266
267Please e-mail bugs to: alet@librelogiciel.com (Jerome Alet)
Note: See TracBrowser for help on using the browser.