From owner-freebsd-rc@FreeBSD.ORG Mon Mar 24 21:49:54 2008 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB89F106564A; Mon, 24 Mar 2008 21:49:54 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id B395D8FC19; Mon, 24 Mar 2008 21:49:54 +0000 (UTC) (envelope-from sam@errno.com) Received: from Macintosh-2.local ([10.0.0.196]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m2OLnrkP041757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Mar 2008 14:49:54 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <47E82201.3000502@errno.com> Date: Mon, 24 Mar 2008 14:49:53 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Doug Barton References: <47E809EE.4080809@errno.com> <47E81D12.5090201@FreeBSD.org> <47E81DD1.8050205@errno.com> <47E820D7.1060804@FreeBSD.org> In-Reply-To: <47E820D7.1060804@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Misty-Metrics: ebb.errno.com; whitelist Cc: freebsd-rc@FreeBSD.org Subject: Re: boot ordering and syslogd X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Mar 2008 21:49:55 -0000 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