[cups.development] Print job not deleting when no output from filter?

[Michael Sweet]

On Aug 9, 2010, at 9:14 AM, Tim Pushor wrote:
> ...
> Now in my case I can work around it by sending a very small minimal PDF 
> file, as it will be absorbed by the file:/dev/null printer but a) this 
> is gross, and b) makes me wonder about print jobs hanging around if 
> filter scripts fail or erroneously generate output that scripts further 
> up the chain can't grok .. Is this the desired behavior of cups?

Yes, if a filter does not succeed we want to hold onto the job so that we can potentially print it later once the problem is resolved.

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair