[cups.general] Printing ps files in fixed order via lpr frontend

[Jan Hubený]

Dne 31.5.2011 03:59, Michael Sweet napsal(a):
> How is the queue configured? I.e. are you printing to a server or ???
>
I am not sure whether I understand your question. Therefore, I apologize 
for following  broad description. We have red hat linux server (v. 5.3), 
the CUPS (v. 1.3.7) is running  on this server. We have around 40 
printers. They are all defined with ppd files. You can see the complete 
cups configuration  in the attachment (cups.tar.gz is gzipped /etc/cups).

Further, we have another linux server. The apache web server is running 
on this server. There are several bash cgi scripts on this server. One 
cgi script is for the technical drawing printing. Parameters of this 
script are printer name and file name.
the printing of the technical drawing makes following command:

    lpr  -P$printer "$file"

Last, we have a java rich client application. This application calls the 
cgi script with web queries. It make one http query per one print 
file/job. It waits until the cgi script finishes (i.e. the lpr command 
inside the script finishes) before making another query.

However, the results are similar when we use more simpler setup which I 
describe in previous mail. The order of the printed  files  on the 
physical printer sometimes is not the same as the order of the print 
jobs (see previous mail).

With regards,

Jan Hubeny
> On May 30, 2011, at 1:33 AM, Jan Hubený wrote:
>
>> Hi,
>>
>> consider following situation:
>>
>> we run CUPS on server with following configuration: redhat linux  5.3.
>> cups 1.3.7, gs 8.70.  We have one folder with technical drawings in
>> postscript format on this server.
>> Let's say that the forder is
>>
>>   /data
>>
>>   and contains several postscript files
>> Name              Size
>> 1.ps              20KB
>> 2.ps              1.5MB
>> 3.ps              20KB
>> 4.ps              5MB
>> 5.ps              300KB
>>
>>
>> We want to print this postscript files in a specified order (1.ps 2.ps
>> 3.ps 4.ps 5.ps).
>> The application which prints this files prints them by invoking
>> following commands:
>>
>> lpr -POCEtds600 /data/1.ps
>> lpr -POCEtds600 /data/2.ps
>> lpr -POCEtds600 /data/3.ps
>> lpr -POCEtds600 /data/4.ps
>> lpr -POCEtds600 /data/5.ps
>>
>> The application waits until each command finishes before invoking next
>> lpr command. Therefore,  we can see the following queue
>>
>> root at users #lpq -POCEtds600
>>
>> OCEtds600 is ready
>> Rank    Owner   Job     File(s)                         Total  Size
>> 1st     user    1326407 1.ps 20     KB
>> 2st     user    1326408 2.ps 1.5    MB
>> 3rd     user    1326409 3.ps 20     KB
>> 4th     user    1326410 4.ps 5      MB
>> 5th     user    1326411 5.ps 300    KB
>>
>> The CUPS then process the OCEtds600 queue and prints the drawings.
>> However, the drawings are printed in different order for example:
>>
>> the output paper sheets on the physical printer are in this order
>>
>> 1.ps
>> 3.ps
>> 2.ps
>> 5.ps
>> 4.ps
>>
>> It seems that the larger files are processed longer than smaller files
>> and the smaller files are printed earlier and skips over the longer files.
>>
>> My question is following: Is there a way to ensure  that the files will
>> be printed in the specified fixed order (i.e. 1.ps 2.ps 3.ps 4.ps 5.ps
>> in our example) on a particular printer?
>>
>> With regards,
>>
>> Jan Hubeny
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> __________ Information from ESET Mail Security, version of virus signature database 6163 (20110529) __________
>>
>> The message was checked by ESET Mail Security.
>> http://www.eset.com
>>
>>
>> _______________________________________________
>> cups mailing list
>> cups at easysw.com
>> http://lists.easysw.com/mailman/listinfo/cups
> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
> _______________________________________________
> cups mailing list
> cups at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups
>
>
> __________ Information from ESET Mail Security, version of virus signature database 6166 (20110530) __________
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>




__________ Information from ESET Mail Security, version of virus signature database 6166 (20110530) __________

The message was checked by ESET Mail Security.
http://www.eset.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cups.tar.gz
Type: application/x-gzip
Size: 362000 bytes
Desc: not available
URL: <https://lists.cups.org/pipermail/cups/attachments/20110531/fb001036/attachment.bin>