root / pykota / trunk / README @ 873

Revision 873, 9.0 kB (checked in by jalet, 21 years ago)

GPL paragraphs were incorrectly (from memory) copied into the sources.
Two README files were added.
Upgrade script for PostgreSQL pre 1.01 schema was added.

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