[cups.bugs] IPP waitprinter stuck waiting in a print class - bug?

[Michael Sweet]

On Jan 18, 2010, at 6:29 AM, Jeff Chua wrote:
> Michael,
> 
> I'm trying to use the IPP waitprinter option and have created a class consisting of 3 printers (lets call this class1). I noticed that when one of the printer is "stuck", the IPP printer (with the waitprinter=true) will get stuck trying to send to  class1.
> 
> 1) create 3 printers (p1, p2, p3) all under "class1"
> 2) create an IPP printer (w1) with option waitprinter=true.
> 3) intentionally cause p2 to "slow" printing be inducing a 200 seconds delay.
> 4) print many times from w1 to class1
> 
> lpstat will show w1 hanging trying to print to class1 because class1 is waiting for p2 to becomes idle.
> 
> Since class1 is a class consisting of 3 printers, it should be considered "idle" because the other 2 printers in its class are idle and can accept new jobs even if one of it's peer is down, so shouldn't w1 continues to print to p1 and p3?

Yup, however if you are printing using the same IPP printer (w1), that printer (locally) is not a class and so only one job will get sent at a time. Only classes get the special multi-job behavior.

If you use "waitprinter=false" and "waitjob=false" on printer "w1", then the jobs will get queued up as fast as possible on the server and all of the printers in the class will be used.

___________________________________________________
Michael Sweet, Senior Printing System Engineer



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20100118/e8c89ce2/attachment.html>