From owner-freebsd-questions  Tue Sep 26 02:59:10 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id CAA29029
          for questions-outgoing; Tue, 26 Sep 1995 02:59:10 -0700
Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA28994
          for <questions@freefall.freebsd.org>; Tue, 26 Sep 1995 02:58:37 -0700
Received: from localhost (localhost [127.0.0.1])
	  by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id KAA03512
	  ; Tue, 26 Sep 1995 10:56:10 +0100
To: David Hedley <hedley@cs.bris.ac.uk>
cc: questions@freefall.freebsd.org
Subject: Re: questions-digest V1 #144 
In-reply-to: Your message of "Tue, 26 Sep 1995 10:02:49 BST."
             <17835.812106169@kiha> 
Date: Tue, 26 Sep 1995 10:56:08 +0100
Message-ID: <3510.812109368@palmer.demon.co.uk>
From: Gary Palmer <gary@palmer.demon.co.uk>
Sender: owner-questions@FreeBSD.org
Precedence: bulk

In message <17835.812106169@kiha>, David Hedley writes:
>My 3Com 3C509 also generates card errors like the one above, but I have
>commented out the line that prints the error in the kernel as I found it
>very annoying and it serves no real purpose - the card works fine. Would it
>be possible for this message to go into the system logs (like it does in
>Linux) as opposed to just blatting it on the screen?

HUH?

Stuff that is dumped on the screen by the kernel should go to syslogd
for logging. It certainly does it out of the box... look in
/var/log/messages. Those boot messages don't appear out of thin air.
If kernel messages like that are not put into your syslogs it's a
local configuration problem.

e.g. this is a kernel printf warning me that I've tried to do a nasty
     to my SCSI CDROM. This also appeared in /var/log/messages ...

Sep 25 19:46:15 palmer kernel: cd0(aha0:6:0): ILLEGAL REQUEST asc:64,0 Illegal mode for this track
Sep 25 19:46:18 palmer kernel: cd0(aha0:6:0): ILLEGAL REQUEST asc:21,0 Logical block address out of range

(the stuff starting `cd0(...' was what actually appeared on the
screen. The bit before that is added by syslog for what should be
obvious reasons)

Gary