Hello, On Aug 22 15:39 Robert Paulsen wrote (shortened):
For a long time now, using SuSE 9.1 through 9.3 (and RedHat before that) I have been printing to my HP LaserJet 2100M without problem. In the past week or so (may have started earlier) I have noticed that print jobs do not come out on the printer until I go over and press the start button. ... I ... Started backend /usr/lib/cups/backend/socket (PID 13747) for job 27.
See http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html "The Backends" why it happens but there is no solution in CUPS. Try to have your network printer switched on and ready to operate before you submit a print job. The usual workaround is a cron job which enables all disabled queues every few minutes but it may lead to a denial-of-service problem. Some quotations from the cups@easysw.com list why it is as is: ---------------------------------------------------------------------
I don't understand the philosophy of taking a printer offline after a failure.
Put simply, we cannot determine whether a file has printed or what has caused the error. The only safe course of action is to stop the printer until the administrator has resolved the problem.
It seems that the scheduler should keep trying to print.
We don't do this by default because we have no way of knowing whether a sporadic error has caused the failure or a problem with the print file.
What is the worst that could happen? The scheduler enters a retry loop, and the backend fails again.
The worst-case scenario is a denial-of-service which prints a lot of duplicate pages. I actually am working on a support call right now for a file that is crashing a PostScript printer - if we did the retry-by-default behavior, you'd use up all of your paper and a lot of toner for errors like that. Again, there is no way for us to determine the cause of the error and so we take a conservative approach.
I am also curious if this behavior (shutting down a print queue) is documented somewhere.
The IDD, SDD, and (IIRC) the SAM describe this behavior. You'll be happy to know that CUPS 1.2 adds an error policy attribute which allows you to configure how CUPS handles these errors... --------------------------------------------------------------------- Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/