I've run into this one. Look at the lpd.conf manpage
 and specifically the following parameters :
  
send_try (default: 3)
              Numbers  of  times  to  try  to  send  a job to the
              printer or remote host.  A 0 value means  an  infi�
              nite number of times.

connect_interval (default: 10 (seconds))
              The time to pause after a failed connection or open
              of the printing device before attempting a new con�
              nection or open.
 
connect_timeout (default: 10 (seconds))
              The time to wait for a device open or connection to
              complete.  A zero value is infinite timeout.

 stalled_time might also be of interest. By simply setting send_try=0
 the job will never drop off.

Joseph Formoso wrote:
> 
> Folks,
> 
>         This morning, our Operations staff found both of our HP8100's
> had console errors.  As a result, it appears that any jobs submitted
> after the errors appeared got dumped off the queue.
> 
>         I would really like it if, when the printers stopped accepting
> jobs (due to paper jams, etc.) that the jobs that were in the queues
> *stayed* in the queues until the problem got cleared.  Is there any way
> to set up the config so that happens?  I feel that I must be missing
> something pretty basic.
> 
>         In any case, the two 8100s are pooled; the relevant chunk of our
> printcap file is thus:
> 
> -------------------------------------------------------
> laser|las|ps|lps|hp8100pool:\
>:sd=/var/spool/lpd/hp8100pool:\
>:sv=hp8100a,hp8100b
> 
> hp8100a|first:\
>:rw:\
>:mx=0:\
>:bp=/usr/local/libexec/filters/psbanner:\
>:lp=foo1.bar.baz%9100:\
>:af=hp.acct:\
>:lf=hp.log:\
>:filter=/usr/local/libexec/filters/ifhp:\
>:ifhp=model=hp8100:\
>:sd=/var/spool/lpd/hp8100a:\
>:ss=hp8100pool
> 
> hp8100b|second:\
>:rw:\
>:mx=0:\
>:bp=/usr/local/libexec/filters/psbanner:\
>:lp=foo2.bar.baz%9100:\
>:af=hp.acct:\
>:lf=hp.log:\
>:filter=/usr/local/libexec/filters/ifhp:\
>:ifhp=model=hp8100:\
>:sd=/var/spool/lpd/hp8100b:\
>:ss=hp8100pool
> -------------------------------------------------------
> 
>         Many thanks for any assistance.
> 
>                                         --Joe
> 
> -----
> Joe Formoso ([EMAIL PROTECTED]),
>   Senior Systems Administrator, IT Department, Stevens Institute of Technology
> 
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------

-- 

 David K Livingstone
 CN Signals and Communications
 10004 104 Ave, 21st Floor
 Edmonton, AB, T5J 0K2
 Ph  : 780 421-6323 Fax : 780 421-6607
 Email: [EMAIL PROTECTED] Text Page : [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.
-----------------------------------------------------------------------------

Reply via email to