From owner-freebsd-hackers Wed Feb 19 17:01:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA02340 for hackers-outgoing; Wed, 19 Feb 1997 17:01:20 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA02331 for ; Wed, 19 Feb 1997 17:01:15 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id LAA11679; Thu, 20 Feb 1997 11:54:36 +1100 Date: Thu, 20 Feb 1997 11:54:36 +1100 From: Bruce Evans Message-Id: <199702200054.LAA11679@godzilla.zeta.org.au> To: joerg_wunsch@uriah.heep.sax.de, skynyrd@opus.cts.cwu.edu Subject: Re: License to kill annoying syslog feature? Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >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? /etc/rc used to do that, but was broken in rev.1.89. The clearing probably should be done immediately after mounting things. Bruce ---------------------------- revision 1.89 date: 1996/05/08 09:25:57; author: jkh; state: Exp; lines: +2 -2 Nuke the nasty cleaning of /var/run after netstart starts - it nukes gated's pid file, for one thing, and is just generally BAD. ----------------------------