root / pykota / trunk / README @ 1965

Revision 1965, 21.8 kB (checked in by jalet, 19 years ago)

Added a note about the requirement of pysnmp version 3.4.3 or 3.4.2

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