[Contents] [Prev] [Next] [Index] [Report an Error]

Tracing Event Policy Processing

Event policy tracing operations track all event policy operations and record them in a log file. The logged error descriptions provide detailed information to help you solve problems faster.

By default, no events are traced. If you include the traceoptions statement at the [edit event-options] hierarchy level, the default tracing behavior is the following:

Important events are logged in a file called eventd located in the /var/log directory.
When the file eventd reaches 128 kilobytes (KB), it is renamed eventd.0, then eventd.1, and so on, until there are three trace files. Then the oldest trace file (eventd.2) is overwritten. (For more information about how log files are created, see the JUNOS System Log Messages Reference.)
Log files can be accessed only by the user who configures the tracing operation.

You cannot change the directory (/var/log) in which trace files are located. However, you can customize the other trace file settings by including the following statements at the [edit event-options traceoptions] hierarchy level:



[edit event-options traceoptions]
file filename <files number> <size size> <world-readable
| no-world-readable> <match regex>;
flag {
all;
configuration;
database;
events;
policy;
server;
timer-events;
}

These statements are described in the following sections:

[Contents] [Prev] [Next] [Index] [Report an Error]