root / pykota / trunk / FAQ @ 1632

Revision 1622, 6.5 kB (checked in by jalet, 20 years ago)

Added support for binary PostScript? through GhostScript? if native DSC
compliant PostScript? analyzer doesn't find any page. This is much
slower though, so native analyzer is tried first.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1PyKota's FAQ :
2
3  # $Id$
4 
5  * I've installed all correctly, I've created users
6    and printers, but when printing nothing works.
7    What is the problem ?
8    The most probable cause for this is that you didn't
9    adapt /etc/pykota/pykota.conf to your own configuration.
10    The file installed by default is just an example, you
11    have to modify it. See the rest of this document to
12    learn how to really diagnose what went wrong.
13   
14  * How can I diagnose the problem when something goes wrong ?
15 
16    Put "LogLevel debug2" in cupsd.conf (usually in /etc/cups/).
17    Then put "logger: stderr", "debug: yes" and
18    "crashrecipient: youremailaddress" in /etc/pykota/pykota.conf.
19    Finally restart CUPS.
20    CUPS' error_log file will now contain many informations which
21    will help diagnose your problem. You will receive failure
22    notices by email, and you can send all this to us for
23    diagnostic.
24 
25  * Why doesn't CUPS under Debian Woody automatically
26    detects PyKota managed devices ?
27   
28    The CUPS version in Debian Woody is 1.1.14 which is a bit
29    too old. To use PyKota with this version, just install
30    your printers as usual in CUPS web interface, and ensure
31    they work fine, then save your changes, and modify
32    /etc/cups/printers.conf manually as explained in
33    PyKota's toplevel README file. Finally restart CUPS,
34    and your printers should be managed by PyKota.
35    Another solution is to install a newer CUPS release.
36   
37  * Is print accounting ever exact ?
38 
39    No. Print accounting is **never** exact, because it depends
40    on external factors like the presence of paper in the printer,
41    the quantity of remaining ink in the print cartridge, paper
42    jams, etc... All these things are very difficult to account
43    for correctly, and no print accounting package deals with
44    these artefacts correctly in all situations.
45    We are however confident that PyKota is one of the more
46    exact print accounting software, because by default it
47    asks the printers for how many pages they have really printed.
48   
49  * Can PyKota account for ink usage ? 
50 
51    No. Actually PyKota doesn't account for ink usage, but this
52    may come in a future release. PyKota only accounts for pages
53    printed and/or money spent.  If ink accounting is a necessity
54    for you, PrintBill is recommended instead of PyKota. PrintBill
55    allows you to bill differently per color, and to bill depending
56    on the percent of the ink covered part of the pages.
57   
58  * What is a 'dumb printer' ?
59 
60    In PyKota, the term 'dumb printer' defines a printer which doesn't
61    understand PostScript, PCL5, PCLXL (aka PCL6) or PDF AND doesn't
62    have an internal page counter, AND for which you don't know how to
63    compute a job's size in number of pages by analyzing its content.
64    Any printer which is not a 'dumb printer' according to the above
65    definition is supported by PyKota.
66
67  * How can I make PyKota work with my non-postscript printer under
68    CUPS ? 
69 
70    From version 1.16alpha7, PyKota includes a CUPS backend which
71    allows you to use any type of printer and any driver, provided
72    your printer is not a 'dumb printer' (see above).
73   
74  * How can I use my 'dumb printer' with CUPS and PyKota. 
75 
76    You have to use a software accounter directive, and
77    create a script which understands your printer's
78    Page Description Language.
79   
80    PyKota natively understands DSC compliant PostScript, PCL5,
81    PCLXL (aka PCL6) and PDF. Support for Binary PostScript is
82    done through GhostScript. More PDLs will be added in the future.
83    However you can always plug your own PDL analyzer in PyKota.
84         
85  * I've got a great number of users. How can I automatically
86    set an initial print quota for them on first print ?
87   
88    You have to define an external policy for unknown users,
89    to automatically add them to the Print Quota database.
90    The sample configuration file contains examples to do this.
91   
92  * What does the --prototype command line option to edpykota do ?
93 
94    This option currently (v1.17) only copies the soft and hard
95    page limits from a template user to other users. This option
96    needs to be updated to new PyKota functionnalities, because it
97    currently lacks.
98   
99  * How can I share print quota between some printers only (not all) ?   
100 
101    To do this you have to put the printers into a printers group, and
102    set quota on the printer group, instead of (or in addition to)
103    the printers themselves.
104   
105  * What is a printer group ?
106 
107     A printer group is exactly like a normal printer, but is
108     unknown by the printing system. You can use printer groups
109     to share print quota between printers.
110   
111  * How can I create a printer group ?   
112 
113    Just use pkprinters, like for normal printers, then create
114    quota entries for users or users groups on it using the
115    edpykota command
116 
117  * How can I put a printer into a printer group ?
118 
119    Use the pkprinters command to do this.
120   
121      $ pkprinters --help
122     
123    Will print the complete help and tell you how to do.
124   
125  * How quota checking and update is done with printer groups ?   
126 
127    Print accounting and quota checking is done for a printer and
128    all the printers groups it belongs to, recursively.
129    If quota is reached on ANY of these printers for the current user,
130    printing is denied.
131   
132  * Is this feature robust ?
133 
134    It should be. However, beware of integrity problems. LDAP has no
135    sense of database integrity, and PostgreSQL constraints have not
136    yet been fully implemented. The code actually *tries* to forbid
137    circular printers groups, but if you create printer groups with
138    another tool (e.g. psql or gq), then you are mostly on you
139    own to not create infinite loops.
140   
141  * How is computed the job's price ? 
142 
143    A job's price is computed with this formula :
144   
145      SUM((NbPages * PricePerPage) + PricePerJob)
146     
147    For current printer and all the printers groups it is
148    a member of, if any, recursively.
149    This may be difficult to grasp, but offers unprecedented
150    flexibility.
151
152  * My question isn't answered there, can you help ? 
153 
154    Sure. Ask your question to the mailing list. If this is a
155    frequently asked question, or if your problem is on the contrary
156    very specific, it will probably be added to this document.
157   
158    You can also ask questions by IRC :
159   
160        /server irc.freenode.net
161        /join #pykota
162       
163Send any new questions to Jerome Alet - <alet@librelogiciel.com>
Note: See TracBrowser for help on using the browser.