PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System)

3.2.3 syslog setup

Set the following to output the interface up/down operation history through the redundant line control as syslog messages.

[Setting file]

/etc/syslog.conf

[Settings]

When enabling message output

Add "*.info" information to the setting file. In this setting, messages are output to the /var/adm/messages file.

# #ident  "@(#)syslog.conf        1.4     96/10/11 SMI"   /* SunOS 5.0 */
#
# Copyright (c) 1991-1993, by Sun Microsystems, Inc.
#
# syslog configuration file.
#
#
*.err;kern.notice;auth.notice                   /dev/console
*.err;kern.debug;daemon.notice;mail.crit;*.info /var/adm/messages

When disabling message output
Delete "*.info" information from the setting file.

# #ident  "@(#)syslog.conf        1.4     96/10/11 SMI"   /* SunOS 5.0 */
#
# Copyright (c) 1991-1993, by Sun Microsystems, Inc.
#
# syslog configuration file.
#
#
*.err;kern.notice;auth.notice                   /dev/console
*.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages

[Setting notification]

After changing the setting file (/etc/syslog.conf), obtain the super-user rights and then issue a reread notification of the definition file to the syslog daemon (syslogd) as shown below:

(1) Example of acquiring the process ID of the syslog daemon

In the following case, 234 becomes the process ID.

# ps -ef | grep syslogd
  root   234     1  0 17:19:04 ?        0:00 /usr/sbin/syslogd

(2) SIGHUP transmission

Send SIGHUP to the process (process ID=234 in the above example) obtained in (1).

# kill -HUP 234

[Others]

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.