From owner-freebsd-current  Sun Mar 26 08:24:26 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19693 for current-outgoing; Sun, 26 Mar 1995 08:24:26 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA19667; Sun, 26 Mar 1995 08:23:43 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA27027; Mon, 27 Mar 1995 02:20:44 +1000
Date: Mon, 27 Mar 1995 02:20:44 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199503261620.CAA27027@godzilla.zeta.org.au>
To: current@FreeBSD.org, mark@grondar.za
Subject: Re: conf/273: syslogd no longer gets loaded at boot time
Cc: freebsd-bugs@freefall.cdrom.com
Sender: current-owner@FreeBSD.org
Precedence: bulk

>> >Description:
>> 
>> At boot time syslogd craps out with "cant bind to requested address"
>> 
>> >How-To-Repeat:
>> 
>> Reboot :-)
>> 
>> >Fix:
>> 	
>> run syslogd as root. A whole bunch of queued messages (hardware id stuff from
>> the boot) gets dumped to the screen.

>Better Fix: move the loading of syslogd to _after_ . /etc/netstart

This is not quite right either:

1) messages logged by the processes started in /etc/netstart may be lost.
2) syslogd complains about /var/run/utmp being removed and a few "wall"
   messages may be lost.

>This is how it was done before the great rc reorganise.

Then it was quite right.  Parts of the apparently chaotic order of
starting up processes were to avoid problems such as the above.

Bruce