ok...DU4.0f PK1 (will be PK2 on monday or tuesday)
we're running bind 8.2.2 patchlevel 5 and syslogd thats bundled with
du40f
the problem is that named every once in a while will decide to
unload...i dont think its core dumping..but its definitely not staying
loaded. Random times and all. Problem is when this happens, syslogd
stops logging. Sending the syslogd pid a HUP signal doesnt help. It
rotates the logs in /var/adm/syslog.dated but wont log. The only way
to get it to log is to kill and restart it.
Has any one else seen this at all?
One other question. Does anyone recommend any TCP Wrappers for
du4.0f? I want to log every single telnet connect attempt.
Thanks.
Received on Fri Dec 17 1999 - 16:29:28 NZDT