[cups] Errorpolicy

ALi osatien at gmail.com
Thu Apr 3 01:17:18 PDT 2014


the backends we use are lpd and socket


and i dont know why the printers get paused :(
The errorpolicy is in retry-job mode, and i dont know why, the printers
gets to paused mode. In pause mode they can not print anything. And as it
is automatic, nobody turns their printer on.

So how can i make that the printers dont get into paused mode? i am trying
to do it with retryjob retryinterval and retrylimit, trying to replicate it
with a printer that doesnt exist. (ip unavailable) but it doesnt work the
printer gets disabled after waiting a bit.

how can i replicate this? and how can i make cups dont put printers into
paused mode




On Thu, Apr 3, 2014 at 10:08 AM, Johannes Meixner <jsmeix at suse.de> wrote:

>
> Hello,
>
> On Apr 3 07:19 ALi wrote (excerpt):
>
>  the printer is going to pause state after some error (low toner etc)
>>
>
> Issues like low toner are inside the printer and in such cases
> the printer itself does what it wants to do.
> Perhaps you can change the printer's built-in behaviour
> directly at the printer (see the printer manual).
>
> In contrast the CUPS ErrorPolicy is about what should happen
> on the CUPS server when the CUPS backend fails there,
> see "ErrorPolicy" at
> http://www.cups.org/documentation.php/doc-1.7/ref-cupsd-conf.html
> and see in particular "Exit Codes" at
> http://www.cups.org/documentation.php/doc-1.7/man-backend.html
>
> Usually the CUPS ErrorPolicy and issues inside the printer
> are unrelated unless you use a special backend that fails
> when there are issues inside the printer.
>
> Kind Regards
> Johannes Meixner
> --
> SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
> HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://www.cups.org/mailman/listinfo/cups
>



More information about the cups mailing list