I wrote: > I've a problem with remote printers and lprng. > Because I've some remote printers, which are sometimes not online, I > want to keep jobs in the queues. I'm a little bit confused about > documentation and the results of searching the web: > > Documentation of 3.8.15 says: > > send_try A num 3 > number of times to try sending > or printing a job. 0 is infinite. > > Okay, send_try=0 is what I want. > > Documentation of 3.8.15 says: > > connect_interval A num 10 > time between open or connection > attempts > > I want a bigger timeout between attempts, so I'm using > connect_interval=100. > > But: > There are only 3 seconds between open ore connection attempts, here is > part of the log: > > cannot open '192.168.0.111%9101' - 'No route to host', attempt 54 at > 2002-11-27- > 00:50:08.280 ## A=root@linux+498 number=498 process=2500 > cannot open '192.168.0.111%9101' - 'No route to host', attempt 55 at > 2002-11-27- > 00:50:11.280 ## A=root@linux+498 number=498 process=2500 > cannot open '192.168.0.111%9101' - 'No route to host', attempt 56 at > 2002-11-27- > 00:50:14.280 ## A=root@linux+498 number=498 process=2500 > > The configuration for the printer in printcap: > > repr4: > :done_jobs=0 > :connect_interval=100 > :send_try=0 > :rw > :sh > :lp=192.168.0.111%9101 > :sd=/var/spool/lpd/repr4 > :force_localhost@ > :fx=flp > > Anybody know, why connect_interval=100 will not be used?
After googeling some days I found the same problem by other people. Is there really no way to tell lprng, to wait between connection trys, if the remote print server is down? There are 3 different scenarios: - Internal print servers (for instance internal HPJetDirect) in network printers. Here we find the message 'No route to host', if the printer is power off. - external print servers like HPJetDirect EX Plus3 If the printer himselve is power off, we find the message 'Connection refused'. If the print server is power off, we find the message 'No route to host'. - Print servers on a *nix system, which are down sometimes. Here we find the message 'No route to host', if the *nix print server is power off. In all 3 scenarios it is only possible at the moment to: 1. Lose jobs (not acceptable), if retry_nolink is off. 2. To live with an connection attempt every 3 seconds (+ connect_grace). It would be very nice, if connect connect_interval will also be used, if there is 'No route to host' or 'Connection refused'. Thanks for reading till the end ;o) tom ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
