On Fri, Dec 28, 2001 at 10:36:10AM -0500, Clint Fast wrote: > [...] I would suspect this is the new done_jobs parameter, introduced in 3.8.3 or thereabouts, but which unfortunately does not have a default that makes it behave the same as older versions. Reconfigure your build: ./configure --with-done_jobs=0 and make again.
John Harper ------------------------------------ Academic Computing Coordinator University of Toronto at Scarborough [EMAIL PROTECTED] > The problem now is that if I send a single/couple prints to a queue, > they will process through the queue (most of the time), but will still > stay in the queue and remark themselves as "done". For example: > > Printer: fax@new-faxserver > Queue: no printable jobs in queue > Server: no server active > Status: job 'cfA733new-faxserver.alliedbuilding.com' save at > 10:02:32.249 > Rank Owner/ID Class Job Files > Size Time > done root A 733 /tmp/mark_statements. > 3690 10:02:32 > > Now, if I sent 100 of these at the same time, they eventually go away, > save for a couple. > Is there a way I can disable this "done" message? BTW, it also keeps > the cf/hf/df files in the queue as well. > ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
