Your problem could be tackled in different ways, depending on the version of CUPS you're running.
More recent versions of CUPS (version 1.2 and above) come with a builtin functionality that could help here. It's called "ErrorPolicy". It's default setting is selected in cupsd.conf, and determines how cupsd should handle print queues which do not behave as expected. You have 3 choices to tag to each queue individually:
- -- Abort this job and proceed with next job in same queue
- -- Retry this job after waiting for N seconds (where N is determined by cupsd.conf's "JobRetryInterval" directive).
- -- Retry current job immediately and indefinitely.
- -- Stop current print queue and keep the job for future printing. This is still the default, unless you define otherwise as per above mentioned alternatives It also was default + only possible behaviour for all queues in previous versions of CUPS (the one you do want to get rid of as per your question).
Additionally, you can set individual ErrorPolicies to each separate print queue. This setting would be noted in the printers.conf file. (Set it from a commandline with
lpadmin -p printername -o printer-error-policy=retry-this-job).
For older versions of CUPS I'd recommend to have a look at
beh, the CUPS BackEnd Handler.
beh is a wrapper which can be applied to any CUPS backend.
Assuming your print queue currently has defined a backend of
socket://192.168.1.111:9100, and it behaves in the way you don't like (being disabled by cupsd from time to time due to network connection problems). With
beh you'd re-define your backend like this:
This would retry a job 20 times in two minute intervals, and disable the queue only when still not succeeding. Or you could do this:
This retries the job 3 times with 5 second delays between the attempts. If the job still fails, it is discarded, but the queue is not disabled. You want to let cupsd try indefinitely to connect to the device? Good, try this:
Try infinitely until printer comes back. Intervals between connection attempts are 30 seconds. The job does not get lost when the printer is turned off. You can intentionally delay printing simply by switching off the printer. A good configuration for desktop printers and/or home users.
Overall, there is no need to mess around with bash scripts, cron jobs,
sudo in order to re-activate CUPS queues going down erratically.