> > On Fri, Mar 10, 2000 at 02:37:18PM -0000, Kenn Humborg mentioned:
> > > My working theory is that syslogging started blocking for some
> > > reason, thus stalling anything that wanted to log anything (which
> > > stalls named, anything with tcpwrappers, mail, news, etc).
> >
> > Can't see that happening. Syslog is supposed to be non-blocking. It's a
> > fire & forget type of mechanism. At least, when I'm logging loads of
> > things, and syslog hasn't had a chance to write them to disk, my program
> > keeps going..
>> Yeah -- and if syslog could be screwed with like this, and it blocked
> other procs, it'd be a big deal firewalls-wise so it would have come up on
> Bugtraq, which it hasn't AFAIK.
Well, I definitely read something about it in the last few months.
Maybe it wasn't bugtraq. It's coming back to me now...
I think the discussion was whether the syslog libc function should
open /dev/log in blocking or non-blocking mode. If it opens it in
blocking mode and syslogd dies, then all apps will block on writing
to /dev/log. Does this ring a bell with anyone?
Later,
Kenn
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
