Nick Barnes wrote: > 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?
That's correct. syslogd uses the LOG_CONSOLE flag to distinguish its own output from other console output, otherwise it would run into an infinite loop logging its own output. Best regards Oliver PS: If you're interested in source code, see the printsys() function in src/usr.sbin/syslogd/syslogd.c. -- 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 "The ITU has offered the IETF formal alignment with its corresponding technology, Penguins, but that won't fly." -- RFC 2549 _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
