From: Charles Funderburk (charles.t.funderburk@mail.sprint.com)
Date: Thu Jul 25 2002 - 17:17:23 EDT
Hello all,
I've looked in the archives and have tried some of the past summary solutions,
but not good.
I noticed that syslog stopped logging after it rotated the last set of logs
this past week.It's a solaris 8 mu4 machine patched with the latest
recommendeds. I've stopped and restarted syslogd, moved the log file and
rebooted, and even copied in a new syslog.conf file from another server to
verify that I didn't have a tab or a unneeded space. Any suggestions would be
welcomed. I'm using the generic syslog.conf file -
*.err;kern.notice;auth.notice /dev/sysmsg
*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages
*.alert;kern.err;daemon.err operator
*.alert root
*.emerg *
# if a non-loghost machine chooses to have authentication messages
# sent to the loghost machine, un-comment out the following line:
#auth.notice ifdef(`LOGHOST', /var/log/authlog, @loghost)
mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost)
#
# non-loghost machines will use the following lines to cause "user"
# log messages to be logged locally.
#
ifdef(`LOGHOST', ,
user.err /dev/sysmsg
user.err /var/adm/messages
user.alert `root, operator'
user.emerg *
)
# BEGIN RAID Manager additions
# DO NOT EDIT from BEGIN above to END below...
user.err /dev/console
user.err /var/adm/messages
# END RAID Manager additions
Thanks!
Charles
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:39 EDT