1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
General printbill FAQs
----------------------
Q: I see complaints about unknown options in my syslog files! Nothing works!
A: You're probably using Mandrake or SuSE with the Foomatic print filter.
Easily fixed... remove the filter_options line in the primary print queue
(you need it in the secondary queue, but it's a very very bad thing in the
primary queue :-)
Q: How do I get those winpopup messages on the Windows clients?
A: Easy - set response_method to smbclient (or mail, smbclient) and edit
your smb.conf to include the following line:
print command = /usr/bin/lpr -P%p %s @@@%m
Otherwise printbill has no way of knowing which host sent the print job.
Q: Is there any way to just bill for the number of pages printed?
A: Yes! Using the new "pagecount" colourspace (not that it's a colourspace,
but for the purposes of this exercise...). Read the man page for printbillrc
to see how to do this (or install the Debian package, which asks you
nicely ;-)
Q: Can administrators get an infinite print quota, but still get print jobs
properly accounted for?
A: Yes - turn the option on using pqm --infinitise <user>.
Q: Why does my stats web page (after clicking on "stats" in the printer
section of the web interface) spew forth raw PNG data?
A: Because you don't have write access to the place where your config file is
telling printbill_grapher to dump the PNGs - so when gnuplot is invoked, it
can't write the output file, so it dumps it to standard output. Solution -
go to graph_png_output_dir (e.g. /var/www/printbill), make sure the web user
has write permissions, and remove any PNG files in that directory.
Q: When I run printbill_grapher, it explodes! What did I do wrong?
A: Probably nothing - print some more files, some of the stats graphs need a
few data points to be able to generate anything meaningful.
Q: Printbill seems to hang sometimes with Windows print jobs... what's
going on?
A: The quality of Windows postscript drivers varies enormously, and the
output from some is so dodgy it can't be interpreted properly by
ghostscript. Best results are generally had with Adobe's generic postscript
driver (download it for your specific Windows version from Adobe's web
site).
Q: Can I use printbill with CUPS?
A: It *may* possible to make CUPS talk to lprng, but I'm not 100% sure how
to do this. Proper CUPS support is being considered for future
development... it is half-way there at the moment. LPRng works pretty well
for most environments.
Q: Is it possible to use printbill with LDAP / MySQL / Jim's Databases?
A: Again, not yet. Hopefully in the future we will abstract the database
functionality so it can use whatever backend you desire - but not yet.
Volunteers are welcome :-)
Q: You're fabulous! I want to send you money! What is the easiest way?
A: If you like Printbill and want to show your gratitude, make a donation to
the Fred Hollows Foundation (cure blindness in the third world by setting up
cheap intra-ocular lens factories and training locals in opthalmic surgery).
The Debian project and the Free Software Foundation can also use your
donations, if you're feeling philanthropic.
|
