On Sat, 14 Jun 2003 [EMAIL PROTECTED] wrote: > Every time a job is printed, lprng scans the entire spool before deciding > to print the next job. It does a DNS lookup on the originating host of > every job. So if you have 5 jobs in the spool, it has to do 5 lookups, > print job #5, do 4 lookups, print job #4, etc.
But why? If there is an IP restriction in lpd.perms on printing, why isn't the first job picked, DNS checked and then printed or rejected. Where is the need check with DNS for every job for each print? > A patch like this would at least put me a step closer to blowing away > these lookups. I did mis-understand a fair bit of what you are doing > (and I haven't kept up, so I'm not sure of the background behind why you > had come up with this), but it is a stepping stone, at the very least. Hmm, in what way? If you store the address in number form in the control file and use IP numbers in your lpd.perms file, there should be no need for lookups, right? Check a few messages back in the message archive, the message I sent my patches as a reply to, and it explains why I needed the features I hacked. Here is a direct URI: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05394.html Henrik ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
