PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Linux) |
Contents
Index
![]() ![]() |
Chapter 3 Environment configuration | > 3.6 Setting Option Function | > 3.6.6 HUB monitoring |
Operation history of the interface up/down can be output as a syslog message. Since this message is output at the INFO level, the following setting is needed:
/etc/syslog.conf
When enabling message output, add "*.info" information to the setting file. In this setting, messages are output to the /var/log/messages file.
# Log all kernel messages to the console. # Logging much else clutters up the screen. #kern.* /dev/console # Log anything (except mail) of level info or higher. # Don't log private authentication messages! *.info;mail.none;authpriv.none;cron.none /var/log/messages # The authpriv file has restricted access. authpriv.* /var/log/secure # Log all the mail messages in one place. mail.* /var/log/maillog |
When disabling message output, delete "*.info" information from the setting file.
# Log all kernel messages to the console. # Logging much else clutters up the screen. #kern.* /dev/console # Log anything (except mail) of level info or higher. # Don't log private authentication messages! mail.none;authpriv.none;cron.none /var/log/messages # The authpriv file has restricted access. authpriv.* /var/log/secure # Log all the mail messages in one place. mail.* /var/log/maillog |
After changing the setting file (/etc/syslog.conf), obtain the super-user rights and then restart to the syslog daemon (syslogd) as shown below:
# /etc/init.d/syslog restart |
For details about how to set the system log, see the system online manuals. Because line monitor error messages are output to the log at the ERROR level, there is no need to make any special settings.
Contents
Index
![]() ![]() |