[edit system]
syslog {
file alarms {
kernel warning;
}
}
Configure the handling of messages of various types, as described in the comments.
Information is logged to two files, to the terminal of user alex, to a remote machine, and
to the console:
[edit system]
syslog {
/* write all security-related messages to file /var/log/security */
file security {
authorization info;
interactive-commands info;
}
/* write messages about potential problems to file /var/log/messages: */
/* messages from “authorization” facility at level “notice” and above, */
/* messages from all other facilities at level “warning” and above */
file messages {
authorization notice;
any warning;
}
/* write all messages at level “critical” and above to terminal of user “alex” if */
/* that user is logged in */
user alex {
any critical;
}
/* write all messages from the “daemon” facility at level “info” and above, and */
/* messages from all other facilities at level “warning” and above, to the */
/* machine monitor.mycompany.com */
host monitor.mycompany.com {
daemon info;
any warning;
}
/* write all messages at level “error” and above to the system console */
console {
any error;
}
}
Configure the handling of messages generated when users issue Junos OS CLI commands,
by specifying the interactive-commands facility at the following severity levels:
•
info—Logs a message when users issue any command at the CLI operational or
configuration mode prompt. The example writes the messages to the file
/var/log/user-actions.
•
notice—Logs a message when users issue the configuration mode commands rollback
and commit. The example writes the messages to the terminal of user philip.
•
warning—Logs a message when users issue a command that restarts a software
process. The example writes the messages to the console.
25Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages
To Next Page
Loading...
Need help?
General
