From owner-freebsd-hackers  Wed Feb 19 15:08:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA25078
          for hackers-outgoing; Wed, 19 Feb 1997 15:08:16 -0800 (PST)
Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA25073
          for <hackers@freebsd.org>; Wed, 19 Feb 1997 15:08:13 -0800 (PST)
Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id PAA29226; Wed, 19 Feb 1997 15:08:10 -0800
Received: from localhost (skynyrd@localhost)
	by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id PAA14698;
	Wed, 19 Feb 1997 15:08:08 -0800 (PST)
Date: Wed, 19 Feb 1997 15:08:08 -0800 (PST)
From: Chris Timmons <skynyrd@opus.cts.cwu.edu>
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
cc: hackers@freebsd.org
Subject: Re: License to kill annoying syslog feature?
In-Reply-To: <Mutt.19970219221145.j@uriah.heep.sax.de>
Message-ID: <Pine.BSF.3.95.970219145658.13262C-100000@opus.cts.cwu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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? 

-Chris