Date: Sat, 4 Jan 1997 11:34:28 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: randyd@nconnect.net (Randy DuCharme) Subject: Re: syslogd failure Message-ID: <Mutt.19970104113428.j@uriah.heep.sax.de> In-Reply-To: <199701040156.TAA06235@nexgen.HiWAAY.net>; from dkelly@HiWAAY.net on Jan 3, 1997 19:56:05 -0600 References: <randyd@nconnect.net> <199701040156.TAA06235@nexgen.HiWAAY.net>
next in thread | previous in thread | raw e-mail | index | archive | help
As dkelly@HiWAAY.net wrote: > Don't know why, but "rm /var/run/log" and restarting syslogd fixed the > problem. Did my filesystem get dirty somehow? No, that's already okay. It's normally done at /etc/rc time. The question is however _why_ syslogd dies in the first place. If you can afford it, i'd suggest to do the following: . kill the default syslogd . rm /var/run/log . switch to an otherwise unused VTY, where it can run undisturbed . start it there with -d, this will make it spit out some more messages, and run in the foreground . once it died, try to find whether you're seeing something on that VTY (do also watch out for the exit status before clobbering it!) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970104113428.j>