On 29/01/2009, at 11:24 PM, John Ferlito wrote:

On Thu, Jan 29, 2009 at 10:49:09PM +1100, Jeremy Visser wrote:
`fuser -u /dev/log` reveals that indeed, syslogd listens on /dev/log.

Funny thing is, if I restart syslogd, and do things that write to the
log, it works fine. I can see the log entries coming through in syslog,
and it's all good. Just after a few hours, it conks out and starts
hanging.

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.


If you haven't already, you could attach strace to syslogd and see what
it's up to, from memory it's strace -p <pid>

also, (if you haven't already) you could try googling syslogd hanging

http://lkml.org/lkml/2005/3/26/37

--

http://chesterton.id.au/blog/
http://barrang.com.au/


--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to