Date: Thu, 20 Feb 1997 06:42:51 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: License to kill annoying syslog feature? Message-ID: <Mutt.19970220064251.j@uriah.heep.sax.de> In-Reply-To: <Pine.BSF.3.95.970219145658.13262C-100000@opus.cts.cwu.edu>; from Chris Timmons on Feb 19, 1997 15:08:08 -0800 References: <Mutt.19970219221145.j@uriah.heep.sax.de> <Pine.BSF.3.95.970219145658.13262C-100000@opus.cts.cwu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
As Chris Timmons wrote: > While you are on the topic of syslog, I've noticed that if a -current or > 2.2 system dies without a normal graceful shutdown, the next startup's > syslogd finds /var/run/log and won't bind to the syslog port with a > 'socket already in use' error or similar. Could /etc/rc safely remove > /var/run/log cruft ahead of starting syslogd? Are you sure your /etc/rc is up to date? rm -f /var/run/log echo ' syslogd.'; syslogd That's from 2.2's /usr/src/etc/rc. -- 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.19970220064251.j>