If /etc/syslog.conf does not exist the syslogd daemon will output all log messages of priority info or higher to the console and to the file /etc/messages. To prevent /etc/messages from getting too large, the syslogd daemon will rotate the contents of /etc/messages through the files /etc/messages.0 through /etc/messages.5. This rotation is done once a week. So the log messages of the current week will be saved in the file /etc/messages and the message logs of the six weeks prior to that are saved in the files /etc/messages.0 through /etc/messages.5.
To prevent large numbers of repeated messages being logged, the syslogd daemon will follow the first instance of a repeated message with the number of times the message was repeated. If a message is repeated over a long time period, the syslogd daemon will wait for increasingly longer intervals before logging the number of repeats. The repeat notification interval starts at 30 seconds and moves quickly to 20 minutes.
Because the /etc/messages file on the live filer contains syslog messages from two filers, the filer uses filer names in the syslog messages to indicate the filer from which the syslog message originated.
For example, if toaster1 takes over toaster2, a message from toaster2 is logged to the /etc/messages file on toaster1, and the message can be similar to the following:
Wed May 6 18:57:52 GMT [toaster2/toaster1]: raid_disk_admin]: Volume vol7 has been added to the system.
Copyright © 1994-2008 NetApp, Inc. Legal Information