From owner-freebsd-hackers Wed Feb 19 21:51:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA19557 for hackers-outgoing; Wed, 19 Feb 1997 21:51:18 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA19545 for ; Wed, 19 Feb 1997 21:51:02 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id GAA24074 for hackers@freebsd.org; Thu, 20 Feb 1997 06:50:30 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id GAA27134; Thu, 20 Feb 1997 06:42:51 +0100 (MET) Message-ID: 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? References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chris Timmons on Feb 19, 1997 15:08:08 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. ;-)