root / pykota / trunk / README @ 1771

Revision 1771, 19.6 kB (checked in by jalet, 20 years ago)

dumpykota can now output datas in the XML format

  • 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 and LPRng
4
5(c) 2003-2004 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 REDISTRIBUTION TERMS IN THE FILE 'LICENSE'
23
24====================================================================
25
26PyKota features :
27-----------------
28
29    Operating systems :
30   
31        - Any Unix-like system as print server.
32           
33        - Any operating system as client.
34           
35    Printing systems :
36   
37        - Supports both CUPS and LPRng as the printing system.
38       
39    Databases :
40   
41        - Supports PostgreSQL as the Quota Storage backend.
42          Complete database creation script in SQL is included.
43       
44        - Supports OpenLDAP as the Quota Storage backend.
45          Complete LDAP schema and sample empty tree are included.
46          Plugging PyKota into your existing LDAP infrastructure
47          is really easy thanks to PyKota's great configurability.
48           
49    Printers :       
50   
51        - Hardware or Software accounting methods are completely
52          configurable.
53         
54        - Supports any printer which can report its internal
55          page counter. Can ask printers for their internal
56          page counter via SNMP, Netatalk, PJL, PS, or any
57          other way.
58          This is completely configurable.
59         
60        - Supports DSC compliant and binary PostScript, PDF, PCL5 (up to),
61          PCLXL (aka PCL6) and ESC/P2 printers natively for software
62          accounting methods. More formats to come.
63           
64    Quota systems :       
65   
66        - Supports printers and printers groups quotas.
67       
68        - Supports users and users groups quotas.
69       
70        - Supports page quotas.
71          Page quotas can be set differently on a per printer
72          and per user/group basis.
73       
74        - Supports account balance quotas in any currency.
75          Account balance quotas can be set on a per user
76          basis. The account balance is shared amongst
77          all printers. The history of payments (positive
78          or negative credits to an user account) is kept.
79         
80        - Page quotas and account balance can be set/reset
81          independantly.
82         
83        - Page quotas and account balances can be set on
84          a per user or per group basis.
85         
86        - Price per page and per job can be set differently 
87          on any printer.
88       
89        - Low level of page quota or account balance are
90          configurable.
91         
92        - Both soft and hard limit with configurable grace delay 
93          can be set for page quota.
94         
95        - Possibility to disable quota enforcement for any user
96          or group, while still keeping page accounting.
97             
98    Administration :       
99   
100        - Powerful administration tools can be used to
101          automate setting or resetting of quotas or
102          account balances at specific intervals.
103         
104        - Administration tools can modify several users, 
105          groups, or printers at once.
106         
107        - Account balances can be set, incremented, or 
108          decremented. History of payments is kept.
109         
110        - Both printers and users can be automatically added on
111          first print in a completely configurable way.
112         
113        - Quota report generator available either from the 
114          command line or in any web browser.
115          The web-based quota report generator can be
116          user/password protected.
117         
118        - Print quote generator can tell users how much 
119          a print job will cost them in advance.
120         
121        - Policy with regard to unregistered users can   
122          be configured for each printer to either deny
123          printing, allow printing, or delegate the
124          decision to any external tool.
125         
126        - Warning and error messages can be automatically 
127          sent via email to the administrator, the user,
128          both, or none.
129         
130        - Warning and error messages' content is completely
131          configurable.
132         
133        - Configuration can be changed without needing to 
134          restart the printing system.
135       
136        - Complete print job history is kept. This can be
137          disabled if needed.
138         
139        - Automated low quota or balance remainder can be
140          scheduled regularly or launched manually.
141         
142        - Powerful data dumper to export datas to other
143          software (spreadsheets for example).
144         
145    User Interface :         
146   
147        - All the command line tools accept the -h | --help
148          command line option which prints all the available
149          options and show usage examples.
150         
151        - Completely internationalized. Actually supports the 
152          English, French, Spanish, Portuguese, Brasilian, Swedish,
153          Thai, Greek, German, and Italian languages. More to come.
154
155====================================================================
156       
157Planned features are described in the TODO file.
158
159Actually two (or an infinity of) page accounting methods are
160implemented :
161
162  - The 'hardware' method consists in querying the printer (via SNMP
163    or Netatalk or any other method of your choice) for its total pages
164    counter.
165   
166    This is done both at the beginning and at the end of a
167    print job. The counters difference is then immediately used to
168    decrease the user's account balance or increase his quota usage.
169   
170  - The 'software' method consists in delegating the computation of the
171    job's size in number of pages to any external command of your choice.
172    The command can read the job's data from its standard input and MUST
173    output the job's size on its standard output. Changes to the user
174    account are reported immediately.
175   
176PyKota is known to work fine with most laser printers, either with
177software accounting, or with hardware accounting if the printer
178supports this.
179
180============================================================
181
182INSTALLATION:
183=============
184
185NB :
186====
187
188  You may learn more about PyKota, if it fits your own organization,
189  its internal working, and some potential performance drawbacks and
190  how to avoid them, in a WiKi administered by Ryan Suarez at :
191 
192    http://webcrossing.macosxlabs.org/webx?14@30.QAu3a5k0c4z.7@.26bf4661
193
194  You may also find the following document interesting :
195 
196    http://es.tldp.org/Tutoriales/doc-openldap-samba-cups-python/
197   
198  This document, written in Spanish by Sergio Gonzalez Gonzalez, 
199  describes the integration of PyKota into an OpenLDAP + Samba
200  + CUPS installation. Even for people who can't read spanish
201  this document is really interesting, and contains lots of
202  screenshots.
203 
204Prerequisite :
205--------------
206   
207  You need to have the following tools installed on the CUPS Server :
208 
209    - CUPS or LPRng
210    - Python v2.1 or above
211    - eGenix' mxDateTime Python extension
212    - The JAXML Python module to be able to dump datas in the XML format.
213    - The Python-SNMP module to query printers for their page counter.
214    - The Python-OSD module to use the graphical print quota reminder.
215    - SNMP tools (specifically the snmpget command) if you prefer to
216      use your own script to request query printers.
217    - Netatalk (specifically the pap command) if you plan to
218      request your printer's lifetime page counter via AppleTalk.
219    - PostgreSQL's PygreSQL Python extension and the PostgreSQL client
220      libraries if you plan to use PostgreSQL as the Quota Storage
221      backend.
222 or     
223    - python-ldap Python module and the OpenLDAP client libraries 
224      if you plan to use OpenLDAP as the Quota Storage backend.
225   
226  On Intel i386 architecture, and for performance reasons, it is
227  strongly suggested that you install the Python accelerator Psyco,
228  available at :
229 
230      http://psyco.sourceforge.net
231     
232  Under Debian :   
233 
234      $ apt-get install python-psyco
235     
236  Other architectures may be supported as well in the future, check   
237  this on Psyco's website.
238 
239  Installing Psyco is not mandatory, but it will speedup PCL5 parsing
240  by almost 3 times. PostScript and PDF parsing can also benefit,
241  but in an almost unnoticeable manner since this part of the code
242  is already optimal. For PCL5 this is a completely different matter,
243  and if you install Psyco you will never regret it !
244  Same remark applies for PCL6 (aka PCLXL) : the parser is completely
245  different, but the performance gain with Psyco is impressive.
246 
247  You may also benefit from having the following tools installed to
248  deal with some printers :
249 
250    - npadmin
251    - netcat
252    - ghostscript
253   
254  You need to have the following tools installed on the Quota Storage 
255  Server :
256 
257    - PostgreSQL
258   
259  or 
260 
261    - OpenLDAP
262   
263NB :   
264
265  PygreSQL must be linked with the PostgreSQL client libraries on
266  the Print Server. The PostgreSQL client libraries' version must
267  match the PostgreSQL version used on the Quota Storage Server.
268 
269or 
270
271  python-ldap must be linked with the OpenLDAP client libraries on the
272  Print Server. The OpenLDAP client libraries' version must match the
273  OpenLDAP version used on the Quota Storage Server.
274 
275  This list of prerequisite software may change in the future, when
276  PyKota will support more functionnalities you will be given
277  alternatives.
278 
279  Of course the Print Server and the Quota Storage Server can be the
280  very same machine if you've got a tiny network, or you can have
281  multiple Print Servers all storing their quotas on the same Quota
282  Storage Server if you've got a bigger network.
283 
284Then :   
285------
286 
287Download the latest PyKota version from the CVS tree on :
288
289    http://savannah.nongnu.org/projects/pykota
290
291Just type :
292
293    python setup.py install
294
295You may need to be logged in with sufficient privileges (e.g. root)
296
297The installation script will now automatically check if some software
298is missing and ask you if you still want to proceed with the
299installation or abort it completely.
300
301Go to the initscripts subdirectory of PyKota's sources, and choose
302the appropriate storage backend for your configuration. Read carefully
303the associated README file and execute the initialization script
304to create an empty PyKota Storage. Upgrade scripts may be
305provided as well.
306
307Copy the conf/pykota.conf.sample and  conf/pykotadmin.conf.sample
308sample configuration files to /etc/pykota/pykota.conf and
309/etc/pykota/pykotadmin.conf (the installation script tries to do
310this for you if needed and you agreed to this action). You need to
311adapt these files to your own needs. Especially you may have to create
312sections named after your own printers, and change the
313administrator's email address which by default is root@localhost.
314Read and try to understand these two very well commented files,
315so that you'll encounter less problems later.
316
317Also be sure to double check that commands that query printers
318for their internal page counter work from the command line
319before using them in PyKota's configuration.
320
321The rest of the installation depends on your printing system :
322
323  - CUPS Printing System :
324 
325    Once and for all :
326   
327        Create a symbolic link to the cupspykota backend
328        in CUPS's backend directory :
329       
330          $ cd /usr/lib/cups/backend
331          $ ln -s /usr/share/pykota/cupspykota cupspykota
332         
333        Restart CUPS so that the new backend can be detected.
334       
335          $ /etc/init.d/cupsys restart
336         
337        or :   
338     
339          $ /etc/rc.d/init.d/cupsysrestart
340         
341        or any similar command depending on your operating system. 
342         
343    For new printers :
344   
345        Go to CUPS management interface (http://localhost:631)
346        and choose the appropriate PyKota managed device depending
347        on the type of printer you use. For example, if your
348        printer is waiting on :
349       
350            socket://myprinter.example.com:9100
351           
352        Then choose :   
353       
354            cupspykota:socket://myprinter.example.com:9100
355           
356        Configure your printer as usual.   
357       
358        Now double check /etc/pykota/pykota.conf
359       
360        You should manually create a section named after the
361        printer you've just added, unless you have set
362        all options globally.
363       
364        The new pkhint command can help you with correct settings
365        for your printers, but don't rely on it because it is still
366        experimental work. To use pkhint, you have to feed it with
367        CUPS' printers.conf file this way :
368       
369          $ pkhint </etc/cups/printers.conf
370       
371        pkhint will try to tell you what is the best accounting
372        method for each printer and will print some lines you'll
373        just have to copy&paste in the appropriate sections in
374        /etc/pykota/pykota.conf
375       
376        That's all.
377   
378    For existing printers :
379   
380        If you had already installed a version of PyKota earlier
381        than 1.16alpha7, then remove the *cupsFilter lines in your
382        PPD files for each printer already managed printers. Each
383        line to remove is of the form :
384       
385          *cupsFilter: "application/vnd.cups-postscript 0 /usr/share/pykota/pykota"
386       
387        This means that each time the pstops filter will be executed, it will
388        pass the job's data through the pykota filter which is present in
389        /usr/share/pykota
390       
391        Don't touch anything else, especially any other *cupsFilter line.
392        Then save each of these files.
393       
394        Then, the easiest is to directly modify the DeviceURI lines
395        in /etc/cups/printers.conf, you just have to put
396        'cupspykota:' in front of what is already on these lines.
397        For example, replace :
398   
399            DeviceURI socket://myprinter.example.com:9100
400       
401        with :   
402   
403            DeviceURI cupspykota:socket://myprinter.example.com:9100
404           
405        or :   
406       
407            DeviceURI cupspykota://socket://myprinter.example.com:9100
408       
409        Save the file and restart CUPS.
410       
411        Here too, you may find it interesting to use the pkhint command as
412        described above to help with manual configuration of the file
413        /etc/pykota/pykota.conf
414
415  - LPRng Printing System :
416 
417    For each printer on which you want to use PyKota :
418   
419        Modify the printer's entry in /etc/printcap : you have to add
420        the three following lines :
421       
422          :achk=true:\
423          :as=/usr/share/pykota/lprngpykota:\
424          :ae=/usr/share/pykota/lprngpykota:\
425         
426        This will tell LPRng to activate accounting, and use the lprngpykota
427        accounting filter both at the start and at the end of printing.
428       
429    When all modifications are done, just save the /etc/printcap file and   
430    restart LPRng :
431   
432          $ /etc/init.d/lprng restart
433         
434        or :   
435     
436          $ /etc/rc.d/init.d/lprng restart
437         
438        or any similar command depending on your operating system. 
439       
440    NB : the pkhint command can't be used with LPRng for now, so you   
441         have to modify /etc/pykota/pykota.conf carefully. The comments
442         in this file will help you.
443     
444Now you can begin to populate the PyKota's database with printers,
445users and groups :
446 
447Add printers and users to the quota system and set their quota values :
448
449Starting from version 1.18alpha2, the preferred command to manage
450printers is named pkprinters
451
452    $ pkprinters --help
453   
454    will tell you how to create, manage or delete printers and
455    printers groups.
456   
457    $ pkprinters --add --charge 0.05 hp2100
458   
459    would add the printer named hp2100 with a price per page
460    of 0.05 unit.
461
462Now set quotas for users on this printer :     
463
464    $ edpykota --add -P hp2100 -S 40 -H 50 user1 ... userN
465       
466    launching edpykota without any argument or with the --help
467    command line option will show you all the possibilities.
468   
469    by default, each user is limited by "quota", this means that on
470    each printer he can have a different soft and hard limit.
471    You may want to limit the user by his account balance value,
472    in which case, the print quota is shared between all printers
473    instead of being different. To do this, use the following :
474   
475    $ edpykota --add -P hp2100 --limitby balance --balance 10 user1 ... userN
476   
477    This will put 10 $ (or Euros, PyKota doesn't care) on each user's account
478    balance, and tell PyKota to limit them by their account balance value.
479    Whenever they print on any printer, their account balance value is
480    decreased by an amount which depends on the particular price per page
481    and per job that you may have defined on the printer with edpykota's
482    --charge command line option.
483    Soft and Hard limits are not used if "--limitby balance" is used,
484    but you can define a "poorman"'s threshold in /etc/pykota/pykota.conf
485    to obtain a similar result (warning message when quota is low).
486
487Restart CUPS or LPRng, for example under Debian GNU/Linux systems :         
488
489    $ /etc/init.d/cupsys restart
490   
491  or :
492 
493    $ /etc/init.d/lprng restart
494       
495Your users now should be able to print but not exceed their
496printing quota.
497
498To see printer quota usage, you can use :
499
500    $ repykota --printer lp
501   
502or :
503
504    $ repykota
505   
506    which will print quota usage for all users on all printers,
507    along with totals, if you are the root user. If you are
508    a regular user, only your own quota report will be produced.
509   
510Quota reports are also available remotely by using the CGI script
511printquota.cgi provided in the cgi-bin/ subdirectory. You can
512also use the CSS stylesheet present in the stylesheets/ subdirectory
513and put it at your web server's DocumentRoot, to benefit from a nicer
514look, especially quota violations will appear in different colors.
515
516For different security concerns, please give a look at the SECURITY
517file which is part of this software.
518           
519============================================================
520
521Mailing list :
522--------------
523
524  A mailing list is dedicated to Pykota, you can subscribe to it
525  or consult its archives at :
526 
527    http://cgi.librelogiciel.com/mailman/listinfo/pykota
528   
529  The mailing list is the preferred way to obtain support, because 
530  all members can help and can also benefit from the solutions
531  proposed by other members.
532 
533  Posts by non-members are usually rejected.
534 
535  The mailing list language is english and only english.
536   
537IRC :   
538-----
539
540  You can also chat with us :
541 
542        /server irc.freenode.net
543        /join #pykota
544       
545  Preferred language on this channel is english, but french     
546  is also accepted. Try to avoid exposing complex problems
547  in french because english speaking people on the channel
548  wouldn't benefit from the solutions.
549 
550  PyKota's main author is known as 'tamere' on IRC.
551   
552============================================================
553   
554Please e-mail bugs to the mailing list at : pykota@librelogiciel.com
555or to the main author at : alet@librelogiciel.com (Jerome Alet)
Note: See TracBrowser for help on using the browser.