root / pykota / trunk / FAQ @ 1191

Revision 1186, 3.1 kB (checked in by jalet, 21 years ago)

General improvements to the documentation.
Email address changed in sample configuration file, because
I receive low quota messages almost every day...

  • 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  * Is print accounting ever exact ?
6 
7    No. Print accounting is **never** exact, because it depends
8    on external factors like the presence of paper in the printer,
9    the quantity of remaining ink in the print cartridge, paper
10    jams, etc... All these things are very difficult to account
11    for correctly, and no print accounting package deals with
12    these artefacts correctly in all situations.
13    We are however confident that PyKota is one of the more
14    exact print accounting software, because by default it
15    asks the printers for how many pages they have really printed.
16   
17  * Can PyKota account for ink usage ? 
18 
19    No. Actually PyKota doesn't account for ink usage, but this
20    may come in a future release. PyKota only accounts for pages
21    printed and/or money spent.  If ink accounting is a necessity
22    for you, PrintBill is recommended instead of PyKota. PrintBill
23    allows you to bill differently per color, and to bill depending
24    on the percent of the ink covered part of the pages.
25   
26  * How can I make PyKota work with my non-postscript printer under
27    CUPS ? 
28 
29    From version 1.16alpha7, PyKota includes a CUPS backend which
30    allows you to use any type of printer and any driver.
31   
32  * How can I diagnose the problem when something goes wrong ? 
33 
34    Put "LogLevel debug2" in cupsd.conf (usually in /etc/cups/).
35    Then put "logger: system" and "debug: yes" in
36    /etc/pykota/pykota.conf.
37    Finally restart CUPS.
38    CUPS' error_log file will now contain many informations which
39    will help diagnose your problem. Also your syslog's output for
40    the LPR facility (usually /var/log/lpr.log) will contain
41    PyKota's debug messages, notably all database related queries
42    and their result, be your database PostgreSQL or OpenLDAP.
43    With these two files the problem can usually be diagnosed within
44    minutes. Send them to the mailing list and wait for an answer.
45   
46  * Some, not all, print jobs are never accounted for, why ?
47 
48    From version 1.16alpha7, you can now use the cupspykota
49    CUPS backend, which ensures that all print jobs will be
50    accounted for. The use of the old pykota filter is deprecated
51    with CUPS. It remains the filter of choice for LPRng though.
52   
53  * When printing from Windows, the jobs are never accounted for,
54    but from *nix they are. Could you explain the reason for this ?
55   
56    First refer to the point above. If this doesn't solve your
57    problem, try to set your print driver to PostScript mode
58    and check the "maximum compatibility" box in its configuration,
59    instead of "maximum speed". Often HP printers come with both
60    a PCL and a PostScript driver under Windows. Don't install the
61    PCL one.
62   
63  * My question isn't answered there, can you help ? 
64 
65    Sure. Ask your question to the mailing list. If this is a
66    frequently asked question, or if your problem is on the contrary
67    very specific, it will probably be added to this document.
68   
69    You can also ask questions by IRC :
70   
71        /server irc.freenode.net
72        /join #pykota
73       
74   
Note: See TracBrowser for help on using the browser.