Re: bind and syslog
In article <19991214104840.A17293@vip.net.pl> you wrote:
> 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?
That's evil. Some daemons really want to be long-running regardless of what
is going on around them, like ntpd.
I can't help but ask...
If the server needs to be so stable that bouncing named is considered harmful,
what are you doing upgrading syslogd?