From owner-freebsd-hackers Wed Feb 19 17:46:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA05356 for hackers-outgoing; Wed, 19 Feb 1997 17:46:36 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA05343 for ; Wed, 19 Feb 1997 17:46:32 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA14132; Thu, 20 Feb 1997 12:14:56 +1030 (CST) From: Michael Smith Message-Id: <199702200144.MAA14132@genesis.atrad.adelaide.edu.au> Subject: Re: License to kill annoying syslog feature? In-Reply-To: from Chris Timmons at "Feb 19, 97 03:08:08 pm" To: skynyrd@opus.cts.cwu.edu (Chris Timmons) Date: Thu, 20 Feb 1997 12:14:55 +1030 (CST) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris Timmons stands accused of saying: > > 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? You should update /etc/rc by hand after a 'make world'. > -Chris > > -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[