Date: Tue, 20 May 2008 18:21:01 +0200 (CEST) From: Oliver Fromme <olli@lurza.secnetix.de> To: freebsd-stable@FreeBSD.ORG, Nick.Barnes@pobox.com Subject: Re: syslog console log not logging SCSI problems Message-ID: <200805201621.m4KGL1WU067028@lurza.secnetix.de> In-Reply-To: <60281.1210842841@thrush.ravenbrook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "And believe me, as a C++ programmer, I don't hesitate to question the decisions of language designers. After a decent amount of C++ exposure, Python's flaws seem ridiculously small." -- Ville Vainio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200805201621.m4KGL1WU067028>