On Thu, Jan 29, 2009 at 11:24 PM, John Ferlito <[email protected]> wrote: > Last time I saw something similar it was on our syslog host. ie many > servers were logging to it. The problem occurred where some of the > servers didn't have reverse DNS and syslogd was hanging trying to > perform reverse lookups.
Interesting. Though I didn't mention it in my O.P., DNS was one of the things I suspected. glenstorm's IPv4 address is a local address, and neither of its IPv6 addresses have reverse DNS (Internode don't provide it), so it doesn't have reverse DNS. It's not a syslogd server, though -- all the logs are local AFAIK. Not sure what to do about checking any further, though. I don't understand reverse DNS very well. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
