From owner-freebsd-rc@FreeBSD.ORG Mon Mar 24 21:57:02 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 A6BD4106566B for ; Mon, 24 Mar 2008 21:57:02 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with SMTP id 2F8E88FC29 for ; Mon, 24 Mar 2008 21:57:02 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 23187 invoked by uid 399); 24 Mar 2008 21:34:40 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 24 Mar 2008 21:34:40 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <47E81D12.5090201@FreeBSD.org> Date: Mon, 24 Mar 2008 14:28:50 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.12 (X11/20080319) MIME-Version: 1.0 To: Sam Leffler References: <47E809EE.4080809@errno.com> In-Reply-To: <47E809EE.4080809@errno.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:57:02 -0000 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. Doug -- This .signature sanitized for your protection