Am 05.10.2022 um 18:17:04 Uhr schrieb Diedrich Ehlerding:
> Danke für Hinweise, wo ich was schrauben könnte.
Ist zwar eklig, aber andere haben das mit nem Skript gemacht:
https://linuxgazette.net/147/misc/lg/2_cent_tip__automatically_reenabling_cups_printer_queues.html
Bei RHEL gibt es auch ne Beschreibung, brauchst aber nen Account.
Relevanter Teil davon:
> Changing Printer Error Policy
>
> Change the ErrorPolicy (if using Red Hat Enterprise Linux 5 or 6) for
> the printer that is having difficulties so that the print job is
> retried. To do this, issue a command like the following: Raw
>
> lpadmin -p <printer> -o printer-error-policy=retry-job
>
> where <printer> is the name of the printer for which you want to
> change the ErrorPolicy. You can also set the ErrorPolicy to one of
> the following values:
>
> abort-job will abort the current job and proceed with the next
> job in the queue without disabling the print queue. retry-job will
> retry the job after waiting for JobRetryInterval seconds, as set in
> /etc/cups/cupsd.conf. The documented value of JobRetryInterval is 30
> seconds, but it is actually 300 seconds as described in CUPS
> JobRetryInterval is 5 minutes in RHEL. retry-current-job will retry
> the failed job immediately and indefinitely. This option is only
> available in RHEL 6 and later versions.
>
> Please note that retry-this-job is not a valid value for ErrorPolicy,
> even though it does appear in some CUPS documentation.
> Changing Default Error Policy
>
> Change the default ErrorPolicy that will be applied to newly added
> printers. To do this, add the following line to the CUPS
> configuration file (/etc/cups/cupsd.conf): Raw
>
> ErrorPolicy retry-job