Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Feb 1997 12:14:55 +1030 (CST)
From:      Michael Smith <msmith@atrad.adelaide.edu.au>
To:        skynyrd@opus.cts.cwu.edu (Chris Timmons)
Cc:        joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org
Subject:   Re: License to kill annoying syslog feature?
Message-ID:  <199702200144.MAA14132@genesis.atrad.adelaide.edu.au>
In-Reply-To: <Pine.BSF.3.95.970219145658.13262C-100000@opus.cts.cwu.edu> from Chris Timmons at "Feb 19, 97 03:08:08 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
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  [[



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702200144.MAA14132>