From owner-freebsd-stable@FreeBSD.ORG Tue May 20 16:21:07 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 677391065680 for ; Tue, 20 May 2008 16:21:07 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id D1E608FC23 for ; Tue, 20 May 2008 16:21:06 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m4KGL2dl067029; Tue, 20 May 2008 18:21:02 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m4KGL1WU067028; Tue, 20 May 2008 18:21:01 +0200 (CEST) (envelope-from olli) Date: Tue, 20 May 2008 18:21:01 +0200 (CEST) Message-Id: <200805201621.m4KGL1WU067028@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, Nick.Barnes@pobox.com In-Reply-To: <60281.1210842841@thrush.ravenbrook.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 20 May 2008 18:21:05 +0200 (CEST) Cc: Subject: Re: syslog console log not logging SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, Nick.Barnes@pobox.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 16:21:07 -0000 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