cups-1.4.2 cupsenable range

[Matthias Ehrig]

Hallo and thanks for the answer.

We use a cups server (for accounting) which all jobs spools from any clients (linux&windows) and prints it in save subnets with accounting (filter accurzc).
On the server there are any queues in stopped state (for special reasons such paper) and will enable only on demand. Thereby jobs are NOT printed in order.
The effect is for any queue. An example for my configuration is:

on server:
lpadmin -p 1_073x-color_special -D "HP_Color_Laserjet_5550" -L "street&room" -E -v accurzc:socket://full_printer_dns -m raw -o printer-error-policy=abort-job -o orientation-requested=3

on clients:
lpadmin -p 1_073x-color_special -D "HP_Color_Laserjet_5550" -L "street&room" -E -v http://full_server_dns:631/printers/1_073x-color_special?waitjob=no -P /afs/.../PPDS/PRIMA/hpclj5550spec.ppd -o printer-error-policy=abort-job -o orientation-requested=3

Options are undertaken from previous cups versions - now we use cups-1.4.2 under Scientific Linux release 6.1 (Carbon) (RHEL6.1).
On clients there are no stopped queues.


> Enabling a stopped/disabled queue should start printing jobs in the order they were submitted if every job was submitted with the same priority.
>
> How is the queue configured? What are you printing to?
>
> On Sep 14, 2011, at 1:33 AM, Matthias Ehrig wrote:
>
> > hi, if a stopped queue starts with cupsenable the job range is very stochastic. It's possible to let the former range after cupsenable ? I Can't found any comment in doc. Thanks for help   Matthias
> > _______________________________________________
> > cups mailing list
> > cups at easysw.com
> > http://lists.easysw.com/mailman/listinfo/cups
>
> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>