My apologies for the very late summary. Below is my original
question, followed by a pair of responses. Thanks to
Rachel Polanskis and Arthur Lehmann for their suggestions.
Recently, one of our hard drives (SS/20, Solaris 2.5.1) was
writing sporadic "Disk not responding to selection" messages (along
with a device name) to the console. Is it possible to capture
these messages using syslog, so I can remotely check for them?
The messages didn't appear in /var/adm/messages or /var/log/syslog
using the default /etc/syslog.conf file.
Along the same lines, I'd like to capture disk sector read error
messages - the kind which appear when a bad sector on the disk
is read. Again, these messages appear on the console, but don't
appear to be logged to the usual places ...
From Arthur A. Lehmann <firstname.lastname@example.org>
You can do lots of things with syslogd, I have ours configured
not only to report ALL messages to a designated "loghost" but also
have things like my HP printers configured to report paper jams and
the like, not to mention other "network" syslogd aware devices. I
have an extensive setup for syslogd and can share it with you if you
like which includes sending messages real time to our Network Management
platform tools. To answer your initial question, try this line in your
You must have at least ONE tab character as the white-space delimiter.
After your edit send a SIG-HUP to the syslogd daemon and watch your
/var/adm/messages file fill up ...
From Rachel Polanskis <email@example.com>
I do this:
# vi /etc/syslog.conf
Note the spaces are tabs! Touch /var/log/debug as root and
restart syslogd after editing ...
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:14 CDT