root / pykota / trunk / README @ 922

Revision 920, 9.9 kB (checked in by jalet, 22 years ago)

Installation script now checks the presence of Netatalk

  • 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 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         
71All the command line tools accept the -h | --help command line option
72which prints all the available options and show usage examples.
73       
74Planned features are described in the TODO file.
75
76Actually only the lazy quota method is implemented. What do I call
77lazy method ?
78
79  The lazy method consists in querying the printer (actually via SNMP
80  or Netatalk) for its total pages counter, just before the beginning
81  of a job, and use this to modify the *preceding* user's quota. So
82  you're always late of one print job, but this is generally ok,
83  especially because a check is also done to see if the current user
84  is allowed or not to print.
85 
86  Problem may theorically arise in batches of successive print jobs by
87  different users when there's no sleep time between two jobs : the
88  used pages may theorically be attributed to an incorrect user in the
89  case that the printer is asked for its page counter at the beginning
90  of a new job and before the end of the previous job. This depends on
91  the printer speed and time between jobs, but so far I've not seen
92  any problem with moderately used printers. This also depends on CUPS
93  internal behavior : if CUPS doesn't begin to send a job to a printer
94  before the previous one is completely printed, then there's no
95  problem.
96 
97  Other querying methods which won't suffer from this possible
98  problem, but probably from other ones ;-) will be implemented in the
99  future.
100 
101PyKota is known to work fine with HP Laserjet 2100 and 2200, and
102Apple LaserWriter 16/600 PS.
103
104It should also work fine with any printer capable of outputing
105its lifetime printed pages counter via either SNMP or AppleTalk.
106
107If your printers don't support SNMP or AppleTalk, then making them
108work with PyKota is up to you. Some sample scripts which can query
109non-SNMP printers for their lifetime page counter are included in
110the ./untested directory. You'll have to test and adapt them though,
111and define them as external requesters in the PyKota configuration
112file. See the sample configuration file to learn how to do that.
113
114============================================================
115
116INSTALLATION:
117=============
118
119WARNING :
120=========
121
122  If you run a PyKota version lower than 1.01, you definitely have to
123  upgrade you Quota Storage Database. Please read the documentation
124  included in the initscripts subdirectory first !
125 
126Prerequisite :
127--------------
128   
129  You need to have the following tools installed on the CUPS Server :
130 
131    - CUPS
132    - Python v2.1 or above
133    - eGenix' mxDateTime Python extension
134    - PostgreSQL's PygreSQL Python extension and the PostgreSQL client
135      libraries.
136    - SNMP tools (specifically the snmpget command) if you plan to
137      request your printer's lifetime page counter via SNMP.
138    - Netatalk (specifically the pap command) if you plan to
139      request your printer's lifetime page counter via AppleTalk.
140   
141  You need to have the following tools installed on the Quota Storage 
142  Server :
143 
144    - PostgreSQL
145   
146  PygreSQL and the PostgreSQL client libraries's versions on the CUPS
147  Server must match the PostgreSQL version used on the Quota Storage
148  Server.
149 
150  This list of prerequisite software may change in the future, when
151  PyKota will support more functionnalities you will be given
152  alternatives.
153 
154  Of course the CUPS Server and the Quota Storage Server can be the
155  very same machine if you've got a tiny network, or you can have
156  multiple CUPS Servers all storing their quotas on the same Quota
157  Storage Server if you've got a bigger network.
158 
159Then :   
160------
161 
162Download the latest PyKota version from the CVS tree on :
163
164    http://savannah.nongnu.org/projects/pykota
165
166Just type :
167
168    python setup.py install
169
170You may need to be logged in with sufficient privileges (e.g. root)
171
172The installation script will now automatically check if some software
173is missing and ask you if you still want to proceed with the
174installation or abort it completely.
175
176Go to the initscripts subdirectory of PyKota's sources, and choose
177the appropriate storage backend for your configuration. Read
178the associated README file and execute the initialization script
179to create an empty PyKota Storage. Upgrade scripts may be
180provided as well.
181
182Copy the conf/pykota.conf.sample sample configuration file to
183/etc/pykota.conf, and adapt this file to your own needs and
184configuration.
185
186Modify the PPD files for each printer on which you want to manage
187print quotas, for example /etc/cups/ppd/lp.ppd :
188
189--- Add the line below exactly as-is somewhere near the top ---
190*cupsFilter:  "application/vnd.cups-postscript 0 /usr/bin/pykota"
191--- Add the line above exactly as-is somewhere near the top  ---
192
193Modify the path to the pykota executable if needed, unfortunately
194you have to supply the correct absolute path here due to CUPS
195internals, or put the pykota executable into /usr/lib/cups/filter
196instead of into /usr/bin.
197
198Do this for each ppd file present in this directory if you want
199to enable quota on every printer.
200         
201WARNING : In the case you've got a non-postscript printer, chances
202          are that the *cupsFilter is already filled-in and points
203          to cupsomatic or such a print filter. In this case please
204          check if you can switch your printer to PostScript mode
205          or if there's a way to make it accept PostScript jobs.
206          If yes then ensure that your workstations uses a PostScript
207          printer driver, and replace the *cupsFilter line with the
208          one pointing to the pykota filter. This should work, but
209          is currently untested.
210          If your printer really needs the original *cupsFilter line
211          then you may not be able to use PyKota easily for now.
212
213Add printers and users to the quota system and set their quota values :
214
215    $ edpykota --add -P printer -S softlimit -H hardlimit user1 ... userN
216       
217    launching edpykota without any argument or with the --help
218    command line option will show you all the possibilities.
219
220Restart CUPS, for example under Debian GNU/Linux systems :         
221
222    $ /etc/init.d/cupsys restart
223       
224Your users now should be able to print but not exceed their
225printing quota.
226
227To see printer command usage, you can use :
228
229    $ repykota --printer lp
230   
231or :
232
233    $ repykota
234   
235    which will print quota usage for all users on all printers,
236    along with totals.
237   
238WARNING : as of today, 2003-02-06, group quotas are not
239implemented.
240
241SECURITY : You should ensure that only the print quota administrator
242           can run the warnpykota command, but this is actually not
243           enforced in the program. Any user able to launch warnpykota
244           could flood over-quota users' email boxes.
245           
246           You should ensure that only the print quota administrator
247           can run the edpykota command, but this is actually not
248           enforced in the program. Otherwise, any user could modify
249           his/her or other people's print quota.
250         
251           launching : chmod 750 /usr/bin/warnpykota /usr/bin/edpykota
252           should make you reasonably safe.
253           
254============================================================
255
256Please e-mail bugs to: alet@librelogiciel.com (Jerome Alet)
Note: See TracBrowser for help on using the browser.