A few days ago I asked if console messages were logged to a file. The original
question is at the end of this mail.
The basic answer is that most console messages can be logged to a file by
updating /etc/syslog.conf and restarting the syslogd daemon. Lines in
syslog.conf that have /dev/console can be duplicated. You can change the
duplicate lines "/dev/console" to a file name of your choice.
Not all console messages can be trapped this way, only those that use
the syslog facility (ref man -s 3 syslog).
/etc/syslog.pid contains the process id of the syslog daemon. Use this as
an argument to kill -1 to restart the syslog daemon.
Someone responded that syslog.conf can also be setup to redirect messages
to another host - no details on this. Also a hint - don't use blanks
in syslog.conf, use tabs instead.
Other references ... man syslog, man syslogd, man syslog.conf
Many thanks to all those who replied ...
Sahir N Siddiqui
Mark S Anderson
Fendor Gnuchev (Ted)
Dave Zavatson
Francis Liu
Marina Daniels
Stephen Potter
Cheryl L Southard
Stephen Harris
Guy Cole
nizar@itd.ssb.com
Jim Meritt
Amy Hollander
> Hello Sun Managers,
>
> various files on Solaris contain details of what has happened on the system ..
>
> /var/adm/sulog details su access
> /var/adm/messages seem to be kernel generated messages
> /var/cron/log details of crontab entries initiated
> last command details who logged in, from where and when
> dmesg details boot messages
>
> Is there any way of obtaining the messages that appear on the console after the
> event - ie, are they logged to a file somewhere? (We are trying to manage
> a "lights out" operation).
>
> Will post a summary.
>
> Thanks in advance.
>
> Regards, Strafford
>
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:56 CDT