Date: Mon, 24 Mar 2008 18:03:44 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: sam@errno.com Cc: dougb@FreeBSD.org, freebsd-rc@FreeBSD.org Subject: Re: boot ordering and syslogd Message-ID: <20080324.180344.106014229.imp@bsdimp.com> In-Reply-To: <47E81DD1.8050205@errno.com> References: <47E809EE.4080809@errno.com> <47E81D12.5090201@FreeBSD.org> <47E81DD1.8050205@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <47E81DD1.8050205@errno.com>
Sam Leffler <sam@errno.com> writes:
: Doug Barton wrote:
: > Sam Leffler wrote:
: >> I tried to use syslog to debug an issue with dhclient and noticed
: >> that syslogd is started too late for it to work. This is because
: >> dhclient operates in a chroot jail so must setup it's connection to
: >> syslogd before privsep work is done. This seems like a general
: >> problem and one that should be fixed.
: >>
: >> Anyone got an idea how to correct this?
: >
: > It's a chicken-and-egg issue because if you need the network to do
: > remote syslog'ing (or syslog'ing to an NFS partition, etc.), you need
: > the network up first.
: >
: > What I've done in similar situations is to modify a copy of
: > dhclient-script to spit out data to a text file. If you need something
: > more robust you could always change the ordering locally. If you need
: > help with that just let us know.
:
: Er, this is a problem that needs to be fixed; not hacked around w/ local
: mods. We are losing logging that makes diagnosing problems hard.
Yes. We need to fix syslogd to be able to start before the network
or even FS are mounted and have the only thing that goes 'bad' be the
data to the missing data sinks (disk, network, etc). A quick fix to
this would be to have syslog get a HUP after each of these events and
start syslogd just as soon as /usr is mounted.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080324.180344.106014229.imp>