Previous section   Next section

Recipe 18.10 Logging Router Syslog Messages in Different Files

18.10.1 Problem

You want the Unix server to send router log messages to a different log file than the local system messages.

18.10.2 Solution

To stop router syslog messages from inundating your local system log files, use the following commands:

local7.info                                               /var/log/rtrlog
*.err;kern.debug;auth.notice;mail.crit;local7.none        /var/log/syslog
*.notice;kern.debug;auth.info;mail.crit;local7.none       /var/adm/messages

18.10.3 Discussion

Most common syslog facilities will log all messages of a certain severity and higher (see Table 18-1) to their generic local system log files by default. However, once you configure your syslog.conf file to store all router log messages to a specific file (in this case, /var/log/rtrlog), you probably want to stop this from occurring. Suppressing router log messages from being stored in your local system log files prevents these messages from cluttering your log files with redundant data.

The first line of the previous example causes the syslog facility to store all router logs to a certain file. However, syslog will continue to archive router messages into the general system log files as well. Note that lines 2 and 3 include a wildcard option (*.err and *.info). These wildcards match the local7 logging facility (and all others as well), causing all log messages of a certain severity level and higher to be stored. To prevent the router logs from being stored in the general system log files, use the local7.none, which will override the wildcard setting.

18.10.4 See Also

Recipe 18.6


  Previous section   Next section
Top