Date: Wed, 21 May 2008 15:16:34 +0100 From: Nick Barnes <Nick.Barnes@pobox.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: syslog console log not logging SCSI problems Message-ID: <74604.1211379394@thrush.ravenbrook.com> In-Reply-To: <200805201621.m4KGL1WU067028@lurza.secnetix.de> from Oliver Fromme <olli@lurza.secnetix.de> of "Tue, 20 May 2008 18:21:01 %2B0200"
next in thread | previous in thread | raw e-mail | index | archive | help
At 2008-05-20 16:21:01+0000, Oliver Fromme writes: > Nick Barnes wrote: > > One of our FreeBSD boxes has a SCSI controller and disk, which showed > > problems earlier this week. There was a lot of of chatter from the > > SCSI driver in /var/log/messages and to the console. However, the > > console is unattended and we only discovered the problem subsequently > > because /var/log/console.log didn't show any of the chatter. > > The console.* syslog facility only logs real console output, > i.e. things written to /dev/console. That does _not_ include > output from the kernel. > > For logging kernel output you have to use the kern.* syslog > facility. OK. So when syslogd directs output to the console, it does not also treat it as console.* output? Thanks for this explanation. I'll modify my syslog.conf accordingly. Nick B
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74604.1211379394>