[cups] Re. Why do filter failures stop jobs instead of aborting them? (Bryan Mason)

[Bryan Mason]

On Fri, 2017-08-11 at 21:18 +0200, Kurt Pfeifle wrote:
> On Fri, Aug 11, 2017 at 9:00 PM, <cups-request at cups.org> wrote:
> 
> [....]
>>    2. Why do filter failures stop jobs instead of aborting them?
>>       (Bryan Mason)
> [....]
> 
> Have you checked the configuration of your queue(s)? There is a
> setting for each queue, where you can define ErrorPolicy: there is a
> choice of abort-job or retry-current-job or retry-job or
> stop-printer.
> 
> You can set the wanted policy for a queue (unless you want to keep
> the default) with lpadmin -o printer-error-policy=<name> -p
> printername [...].
> 

The printer-error-policy only comes in to play when the backend exits
with an error.  In this case, the IPP backend on the client isn't
exiting because it's still waiting for the job on the "server" to
complete, abort, or be canceled.

~ Bryan