- Downloads
- traceoptions
- Related Topics
- Tracing Event Policy Processing
traceoptions
Syntax
- traceoptions {
- file <filename> <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
- flag flag;
- no-remote-trace;
- }
Hierarchy Level
- [edit event-options]
Release Information
Statement introduced in JUNOS Release 7.5.
Description
Define tracing operations for event policies.
Default
If you do not include this statement, no event-policy-specific tracing operations are performed.
Options
-
filename—Name of the file to receive the output of the tracing operation. All files are placed in the directory /var/log. By default, commit script process tracing output is placed in the file eventd. If you include the file statement, you must specify a filename. To retain the default, you can specify eventd as the filename.
-
files number—(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed and compressed to trace-file.0.gz, then trace-file.1.gz, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
-
If you specify a maximum number of files, you also must specify a maximum file size with the size option and a filename.
- Range: 2 through 1000
- Default: 3 files
-
flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:
- all—Log all operations
- configuration—Log reading of configuration at the [edit event-options] hierarchy level
- events—Log eventd processing
- database—Log events involving storage and retrieval in events database
- server—Log communication with processes that are generating events
- timer-events—Log internally generated events
-
match regular-expression—(Optional) Refine the output to include lines that contain the regular expression.
-
size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed and compressed to trace-file.0.gz. When the trace-file again reaches its maximum size, trace-file.0.gz is renamed trace-file.1.gz and trace-file is renamed and compressed to trace-file.0.gz. This renaming scheme continues until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
-
If you specify a maximum file size, you also must specify a maximum number of trace files with the files option and filename.
- Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
- Range: 10 KB through 1 GB
- Default: 128 KB
-
world-readable—(Optional) Enable unrestricted file access.
Required Privilege Level
maintenance—To view this
statement in the configuration.
maintenance-control—To
add this statement to the configuration.
