I've got a print queue with an lp entry for a printer who's DNS name was removed.
Someone sent print to the queue, and of course LPRng can't resolve the name to contact the printer. This works properly. As an unintended consequence, LPRng has brought our DNS server to its knees with a tight loop of dns lookups that fail for the name that no longer exists. We're talking hundreds of lookups a second, being sent by a 2.4 ghz server to an old 400 mhz DNS box. It didn't stand a chance. =] Obviously I'll correct my printcap, however I don't think the tight loop to the DNS server was intended to work quite like that. I've tried updating my connect_interval to 5 seconds, but it did not change the behavior. I'm running 3.8.26 on Redhat ES 2.1. Russell ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
