Today, after upgrading BIND to 8.1.2, I had an incredibly odd event occur. Starting named from a remote telnet session would kill syslogd. I was able to re-create this about 25 times (even after cold and warm boots) before the problem went away by itself. During this time starting named on the local console did NOT kill off syslogd. Is this a known bug with something? I find it strange that it continued even after starting up the system from a power off state. I don't feel it was a hardware problem as I did several diagnotics on the machine while this was happening. I am using: Kernel 3.0.35 BIND 8.1.2 Sysklog 1.3-25 I can no longer re-create this so I can't find out if it only happens with these versions. Does anyone know what was happening? Or what to do if it happens again? Many thanks in advance. -Mike - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
