Patrick Powell wrote: > > > > Why does "release" start the queue instead of just sending one single job? > > Is there a way around this? > > This was wanted by users who would 'release' a job and then wonder why > it did not get printed. > > I look in my notes that there is the usual 'be it on your heads, guys' > warning about this. > > Sigh... > My question wasn't why releasing the job caused that job to be sent, but rather (I guess) why there isn't a start-the-queue-for-this-one-job-only function built in.
-- - 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. -----------------------------------------------------------------------------
