From owner-freebsd-current@FreeBSD.ORG Mon May 11 20:13:37 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4DDC10657C5 for ; Mon, 11 May 2009 20:13:37 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 733E98FC1D for ; Mon, 11 May 2009 20:13:37 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n4BKDaO9088903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 May 2009 13:13:37 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <4A0886F0.6030605@freebsd.org> Date: Mon, 11 May 2009 13:13:36 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.21 (X11/20090411) MIME-Version: 1.0 To: Chuck Swiger References: <49FE1826.4060000@FreeBSD.org> <49FE29A4.30507@root.org> <49FE5EC8.3040205@FreeBSD.org> <20090505091914.GA94521@server.vk2pj.dyndns.org> <4A00669A.10105@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: Peter Jeremy , FreeBSD-Current Subject: Re: Fighting for the power. [syslogd] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2009 20:13:38 -0000 Chuck Swiger wrote: > Hi-- > > On May 5, 2009, at 9:17 AM, Sam Leffler wrote: >> Regarding syslogd, I've considered adding support to batch/buffer >> writes to workaround a problem that I consider rather important: >> syslogd is not started early enough in the boot so it's not available >> to log msgs from other applications. In particular I hit this >> because wpa_supplicant logs via syslog but when it's started at boot >> syslogd isn't available and since wpa_supplicant operates in a >> chroot'd environment it cannot defer connecting until syslogd has >> started up so nothing is ever logged. >> [ ... ] > > > You can use -l flag to syslogd to create additional logging sockets > under your chroot'ed filesystem tree, similar to the way named & ntpd > uses it; see syslogd_precmd() in /etc/rc.d/syslogd.... > > Regards, Blech, thanks. That might be a stopgap solution but it still doesn't allow syslogd to be started earlier which is what is needed for many/most setups. syslogd has mountcritremote as REQUIRE to handle diskless setups but IMO this should be (at least) configurable. But rather than argue this nonsense I think the better solution is to do what I suggest so syslogd can be started very early and capture everything available (e.g. your suggestion still loses msgs logged while setting up nfs mounts). Sam