Hi *, 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. The cure is to restart the bind, but on busy servers its not a very good solution. I haven't checked that in the bind sources, but I suppose it just opens the connection to the syslogger but never closes it until it's shut down. As I don't expect bind to be fixed in that respect any soon now, perhaps it would be better to just make the syslogd daemons restart all "affected" programs when doing an upgrade and/or restarting the syslog daemon? marek
Attachment:
pgpUzZZihq4nT.pgp
Description: PGP signature