[cups.development] Only one job queueing between cups queues

[Michael Sweet]

You can add "waitjob=false" to the printer's device URI on the client so that it doesn't wait for the job to complete. Note, however, that you'll need to cancel jobs directly on the server machine since the client will no longer have access to the jobs...

On May 16, 2011, at 2:34 PM, David Hobley wrote:

> I have a network whereby one machine can't see another printer, so I have set up the queues on the first machine to point to a cups on a second machine which can see the printer. All this is working.
> 
> The issue I have is that if I have 25 jobs queued in the cups print queue on the first machine, it is drip feeding 1 job at a time to the cups print queue on the second machine. Once that job has finished printing, it will send the next job.
> 
> Is there any way to ensure that the second machine can accept all the jobs in the queue from the first machine as the time taken to print would be massively reduced if we could queue them all on the second machine while the printing is happening?
> 
> Cheers,
> David
> _______________________________________________
> cups-dev mailing list
> cups-dev at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups-dev

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair