Problems? Is your data what you think it is? | |
PerlMonks |
Re^4: how to resolve IP's in an HTTPd that doesn't resolve them?by taint (Chaplain) |
on Jun 13, 2018 at 21:54 UTC ( [id://1216595]=note: print w/replies, xml ) | Need Help?? |
Thanks for your elaborate reply, afoken ! Timely (HOST) resolution is not a problem on my servers. In fact I wrote (finally finished) a little resolver in about 160 lines ( C source ). That'll turn a file of 255 IP addresses into HOTS name(s), in under ~1 second, on standard CPE. Even faster if given a fatter "pipe". It does so accurately. It is slower, of course, on slower connections, or on bad / unmanaged addresses. Tho I could add a time threshold to the resolver. I haven't bothered, as I only use it for post-processing. So, it would seem from your response; that you'd recommend using a pipe. If my intent is to process the (connecting) IP addresses in real-time. While I had hoped to avoid that. I guess I'm not terribly surprised. Speaking of the Apache HTTPd; it's interesting that Apache doesn't have, or choose the use of a pipe. As it happily logs resolved IP addresses to it's log(s), from all my experiences with it. Maybe I'd do well to give it's source a look over. For possible clues. Thanks again, afoken, for taking the time to reply! Evil is good, for without it, Good would have no value
In Section
Seekers of Perl Wisdom
|
|