Re: LPRng: save_on_error
From [EMAIL PROTECTED] Mon Mar 25 07:43:21 2002 From: Dave Lovelace [EMAIL PROTECTED] Subject: LPRng: save_on_error To: [EMAIL PROTECTED] Date: Mon, 25 Mar 2002 09:56:33 -0500 (EST) OK, this may be a dumb question. We recently, for the first time, started seeing a problem that's been discussed in this list: the printer is busy, or out of paper, or off, and jobs are removed from the queue because of this. The solution given, which we've now implemented, was to set save_on_error in lpd.conf. Up to a point, this works. The jobs no longer vanish out of the queue. Instead, they sit there saying ERROR: removing job due to errors. The only way I've found to actually print them is to identify the data file in the spool directory, copy it out, print that. This isn't acceptable. I'm sure there's a way around this, but I can't find it. If I do an lpc release on them, they sit there in the queue with a rank listing remove (and I think they're eventually removed, though I'm not sure). lpc redo (lpc release is for held jobs) What should I be doing? I've got people breathing fire down my neck on this. -- - Dave Lovelace [EMAIL PROTECTED] [EMAIL PROTECTED] lpc: Illegal option '=' usage: lpc [-a][-Ddebuglevel][-Pprinter][-Shost][-Uusername][-V] [command] with no command, reads from STDIN -a - alias for -Pall -Ddebuglevel - debug level -Pprinter- printer -Pprinter@host - printer on lpd server on host -Shost - connect to lpd server on host -Uuser - identify command as coming from user -V - increase information verbosity commands: active(printer[@host])- check for active server abort (printer[@host] | all) - stop server class printer[@host] (class | off) - show/set class printing disable (printer[@host] | all) - disable queueing debug (printer[@host] | all) debugparms - set debug level for printer down (printer[@host] | all) - disable printing and queueing enable(printer[@host] | all) - enable queueing flush (printer[@host] | all) - flush cached status hold (printer[@host] | all) (name[@host] | job | all)* - hold job holdall (printer[@host] | all) - hold all jobs on kill (printer[@host] | all) - stop and restart server lpd (printer[@host])- get LPD PID lpq (printer[@host] | all) (name[@host] | job | all)* - invoke LPQ lprm (printer[@host] | all) (name[@host]|host|job| all)* - invoke LPRM msg printer message text - set status message move printer (user|jobid)* target - move jobs to new queue noholdall (printer[@host] | all) - hold all jobs off printcap (printer[@host] | all) - report printcap values quit - exit LPC redirect (printer[@host] | all) (printer@host | off )* - redirect jobs redo (printer[@host] | all) (name[@host] | job | all)* - reprint jobs ^^ release (printer[@host] | all) (name[@host] | job | all)* - release jobs reread- LPD reread database information start (printer[@host] | all) - start printing status(printer[@host] | all) - status of printers stop (printer[@host] | all) - stop printing topq (printer[@host] | all) (name[@host] | job | all)* - reorder jobs up(printer[@host] | all) - enable printing and queueing diagnostic: defaultq - show default queue for LPD server defaults - show default configuration values lang - show current i18n (iNTERNATIONALIZATIONn) support client (printer | all) - client config and printcap information server (printer | all) - server config and printcap - 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. -
LPRng: save_on_error
OK, this may be a dumb question. We recently, for the first time, started seeing a problem that's been discussed in this list: the printer is busy, or out of paper, or off, and jobs are removed from the queue because of this. The solution given, which we've now implemented, was to set save_on_error in lpd.conf. Up to a point, this works. The jobs no longer vanish out of the queue. Instead, they sit there saying ERROR: removing job due to errors. The only way I've found to actually print them is to identify the data file in the spool directory, copy it out, print that. This isn't acceptable. I'm sure there's a way around this, but I can't find it. If I do an lpc release on them, they sit there in the queue with a rank listing remove (and I think they're eventually removed, though I'm not sure). What should I be doing? I've got people breathing fire down my neck on this. -- - 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. -
Re: LPRng: save_on_error
Hi Dave I think an lpc redo on the job will get it going again Regards Alan Dave Lovelace wrote: OK, this may be a dumb question. We recently, for the first time, started seeing a problem that's been discussed in this list: the printer is busy, or out of paper, or off, and jobs are removed from the queue because of this. The solution given, which we've now implemented, was to set save_on_error in lpd.conf. Up to a point, this works. The jobs no longer vanish out of the queue. Instead, they sit there saying ERROR: removing job due to errors. The only way I've found to actually print them is to identify the data file in the spool directory, copy it out, print that. This isn't acceptable. I'm sure there's a way around this, but I can't find it. If I do an lpc release on them, they sit there in the queue with a rank listing remove (and I think they're eventually removed, though I'm not sure). What should I be doing? I've got people breathing fire down my neck on this. -- Alan O'Keefe O'Keefe Systems Consulting email: [EMAIL PROTECTED] Phone: +61 413 517168Fax:+613 97408893 - 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. -
Re: LPRng: save_on_error
hi, did you set # Purpose: keep the last NN done jobs for status purposes # default done_jobs= 1 (INTEGER) done_jobs= 0 in the lpd.conf file ??? regards ~christoph On Thu, 14 Feb 2002, Jackson Shea wrote: I had posted earlier about the symptom of persistent job files in 3.8.3, 3.8.5 and now 3.8.6. I had thought it might have to do with the IPP but it was actually the :save_on_error flag in the printcap [or save_on_error in the lpd.conf]. lpc doesn't report any errors on the jobs and yet when save_on_error is enabled, the jobfiles persist forever. We don't observe this symptom with save_on_error enabled in 3.6.26. Any insights? thanks in advance. jackson shea portland state university - 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. - - 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. -
LPRng: save_on_error
I had posted earlier about the symptom of persistent job files in 3.8.3, 3.8.5 and now 3.8.6. I had thought it might have to do with the IPP but it was actually the :save_on_error flag in the printcap [or save_on_error in the lpd.conf]. lpc doesn't report any errors on the jobs and yet when save_on_error is enabled, the jobfiles persist forever. We don't observe this symptom with save_on_error enabled in 3.6.26. Any insights? thanks in advance. jackson shea portland state university - 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. -
