1 |
Alan Mackenzie <acm <at> muc.de> writes: |
2 |
|
3 |
|
4 |
|
5 |
> So, thanks for the email, it brought me back to sanity. |
6 |
|
7 |
|
8 |
A few things to remember. Always check that cupsd is running. |
9 |
(# rc-status). You may need to stop and start the cupsd. |
10 |
|
11 |
Go to the /etc/cups dir and make a second copy of the *.conf files |
12 |
and any others that you use. I give mine a .date <actual date> |
13 |
string, so as to make recovery trivial in the future. Also it's |
14 |
easy to 'scp' those files around to machines if/when necessary. |
15 |
The cups gui interface just modifies those files. |
16 |
|
17 |
Last, become familar with http://localhost:631/ |
18 |
to use the everychanging cups interface to manage your |
19 |
networked and printing resources. |
20 |
|
21 |
If you have HP printers, install this: net-print/hplip |
22 |
|
23 |
One last nuance with cups. Sometimes cupsd is running but the cups |
24 |
software has stop printing. Go to the admin section of cups |
25 |
(http://localhost:631/) and just start the printer again; it's |
26 |
a bug_anomoly I have seen too many times. |
27 |
|
28 |
Really, it's not that difficult with these tidbits to manage and recover |
29 |
functional printing. Using dbus as a flag setting never hurts either |
30 |
and check your cups flag settings. Use the ethernet port in lieu |
31 |
of the usb port, imho, if you have both on any given printer...... |
32 |
|
33 |
|
34 |
hth, |
35 |
James |