Date: Mon, 24 Mar 2008 14:49:53 -0700 From: Sam Leffler <sam@errno.com> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-rc@FreeBSD.org Subject: Re: boot ordering and syslogd Message-ID: <47E82201.3000502@errno.com> In-Reply-To: <47E820D7.1060804@FreeBSD.org> References: <47E809EE.4080809@errno.com> <47E81D12.5090201@FreeBSD.org> <47E81DD1.8050205@errno.com> <47E820D7.1060804@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton wrote: > Sam Leffler wrote: >> 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. > > There is a purpose for the order as it exists, so I would argue that it > is not a problem that needs to be fixed. However I'll let others respond > now. > > Doug > I am fully aware of the ordering constraints but if we are to depend on syslogd for logging messages then this cannot remain. This is really a byproduct of using privsep in various applications and it may be that we need to come up with a solution whereby privsep support learns how to deal with this problem. But saying "it's not a problem that needs to be fixed" is utterly lame. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47E82201.3000502>