You can use Wireshark to record net traffic on port 9100 to verify the order they are sent.
On 10/5/10, George Gallen <ggal...@wyanokegroup.com> wrote: > the debug info shows they were sent to the printer in the numerical unix > job# order. > I disabled the printer, sent the jobs again, and the unix job# order was the > same > as the order sent, I renabled the printer and when the jobs printed they > were > in random order, according to the cups log, they were sent in the correct > order. > > So it looks like it's the receiving print server that is sending them in > random > order to the printer, of course the admin for that server swears it does > FIFO... > > Thanks for the debug tip... > >> -----Original Message----- >> From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- >> boun...@listserver.u2ug.org] On Behalf Of Steve Romanow >> Sent: Saturday, October 02, 2010 12:51 PM >> To: U2 Users List >> Subject: Re: [U2] CUPS printing and sequence of jobs >> >> Maybe turn the logging up a notch and verify the order they are being >> submitted? It might not be considered "submitted" until it finishes >> spooling, where a large job can be surpassed by smaller jobs. We would >> not really want it to "block" on large print jobs. Take for instance >> you start spooling an invoice run that may take 5-6 minutes to spool, >> you do you not want to process any other jobs while this thing is >> transferring to the queue? >> _______________________________________________ >> U2-Users mailing list >> U2-Users@listserver.u2ug.org >> http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- Sent from my mobile device _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
