Juniper JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010 User Manual

match “!(.*snmpd.*)”;
}
file snmpd-errors {
daemon error;
match “.*snmpd.*”;
}
Related Topics Single-Chassis System Logging Configuration Overview•
• Examples: Configuring System Logging
Disabling Logging of a Facility
To disable the logging of messages that belong to a particular facility, include the facility
none statement in the configuration. This statement is useful when, for example, you
want to log messages that have the same severity level and belong to all but a few
facilities. Instead of including a statement for each facility you want to log, you can include
the any severity statement and then a facility none statement for each facility that you
do not want to log. For example, the following logs all messages at the error level or
higher to the console, except for messages from the daemon and kernel facilities.
Messages from those facilities are logged to the file /var/log/internals instead:
[edit system syslog]
console {
any error;
daemon none;
kernel none;
}
file internals {
daemon info;
kernel info;
}
Examples: Configuring System Logging
Log messages about all commands entered by users at the CLI prompt or invoked by
client applications such as Junos XML protocol or NETCONF clients, and all authentication
or authorization attempts, both to the file cli-commands and to the terminal of any user
who is logged in:
[edit system]
syslog {
file cli-commands {
interactive-commands info;
authorization info;
}
user * {
interactive-commands info;
authorization info;
}
}
Log all changes in the state of alarms to the file /var/log/alarms:
Copyright © 2010, Juniper Networks, Inc.24
Junos 10.3 System Log Messages Reference

Juniper JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010 Specifications

General

Brand	Juniper
Model	JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010
Category	Software
Language	English