Cups scheduler do not start backend for each filefor jobs with printmultiple files

Mario Goppold ml at goppold.net
Wed Jul 28 00:18:23 PDT 2010


Thank you for your assistance.
In other words I have to deal with $CUPS_REQUESTROOT/d(.*)-([0-9][0-9][0-9]) like I did before? That answered the question why the filenames are not dropped down to the backend too.

Mario

> On Jul 27, 2010, at 6:28 AM, Mario Goppold wrote:
> > Hi,
> >=20
> > for jobs with more than one file the filter chain is called for each =
> file but there ist only one call for the backend of the whole job.
> >=20
> > Is this supposed to be like this?
>
> Yes, otherwise multiple-file jobs (and this includes jobs with banner =
> pages) can end up with intervening jobs on the printer.
>
> Consider:
>
>     Client A -> Printer
>     Client B -> Printer
>
> If Client A and Client B both have jobs pending for the same printer, =
> each client needs to hold a connection to the printer for the entire =
> job, otherwise the other client's jobs can get mixed in...
>
> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
>
>





More information about the cups mailing list