Perventing Interleaved Print Jobs

[Anonymous]

Yes, I dare try!  I dare!


> Anonymous wrote:
> >
> > BACKGROUND: running cups-1.1.23 on solaris, with serveral network printers configured for device=AppSocket/HP JetDirect as type=socket://<IP address>.  These printers have PPD files which CUPS is configured to use,  and JobSheets is configured for banner "standard."
> >
> > PROBLEM: when another print server on the network (VMS) prints jobs to a given printer, say printer A, and the cups server sends a job to printer A while the job from the VMS server is in progress, the jobs get interleaved.  This frustrates users since large print jobs from one server make small print jobs from another one hard to find (even with banners).
> >
> > QUESTION: since there's no common queue in this scenario, is there a way to configure CUPS so either a. it queues local jobs until it detects printer A becomes "ready", before sending it's next job (sounds iffy), or b. something else I haven't thought of?
>
> This will get better with CUPS 1.2. In the meatime you could use the alternate pstops filter
> which does it's own banner pages (activated by a special option). If you dare to try that and have
> questions, feel free to ask me.
>
> Helge
>
> --
> Helge Blischke
> Softwareentwicklung
> SRZ Berlin | Firmengruppe besscom
> http://www.srz.de