Fighting for the power. [syslogd]

Chuck Swiger cswiger at
Mon May 11 19:39:06 UTC 2009


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....


More information about the freebsd-current mailing list