I've got a little problem here. I sometimes need to be able to stop a printer, and then release jobs to it one at a time, in an order of my choosing.
I do "lpc stop testprinter", and it stops the printer. Fine so far. There are several jobs in the queue. I do (say) "lpc release testprinter 485" to print job ID 485. It prints. So far so good. But the printer has now been restarted, and other jobs follow immediately. I needed to print job 364 and no other at this point. I suppose I can do a holdall on the printer, individually hold the jobs that are already queued up, release jobs one at a time (do I need to unhold them to do that?), and then eventually do a noholdall and individually unhold all the held jobs that are left. That means a lot of keeping track, as there might be jobs which were held before I started this & which are supposed to *stay* held, for example, until someone else is ready. Why does "release" start the queue instead of just sending one single job? Is there a way around this? Any help will be greatly appreciated. This is going to be a really big headache for me if I can't find a reliable way around it VERY soon. -- - Dave Lovelace [EMAIL PROTECTED] [EMAIL PROTECTED] ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
