[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bind and syslog

* Steve Greenland said:
> On 14-Dec-99, 03:48 (CST), Marek Habersack <grendel@vip.net.pl> wrote: 
> >   As some of you might have noticed that already, bind has a small annoyance
> > related to syslog. Specifically, when the syslog daemon (no matter which one
> > it is) is restarted, bind loses connection to it and further log messages
> > are output to the console. 
> IMO, this is a bug in syslog(3). IIRC, it only affects programs that
No, it isn't. You can't expect syslogd to keep an open connection to
/dev/log when it is being restarted...

> use openlog(3) - if you just call syslog, (taking the default facility,
> etc.), then it doesn't happen, presumably because in that case syslog
Calling just syslog is what causes much mess to happen - too many programs
use it and then your logs are full of messages mixed from many irrelevant
sources... openlog/syslog/closelog is the appropriate sequence.

> takes care of the necessary open(). The work around is to catch SIGPIPE
> and re-do the openlog(), but it's stupid that each client should have to
The workaround is not to keep an open connection to the syslog. System log
messages should be as infrequent as possible, so there's no real penalty in
invoking openlog/syslog/closelog each time a message is logged.


Attachment: pgpuDeVdgI6It.pgp
Description: PGP signature

Reply to: