traceoptions (Commit, Op, and SNMP Scripts)
Syntax
traceoptions { file <filename> <files number> <size size> <world-readable | no-world-readable>; flag flag; no-remote-trace; }
Description
Define tracing operations for commit, op, and SNMP scripts.
Default
If you do not include this statement, the default operation
during script execution is to log important events in the default
trace file for that script type, because the traceoptions events
flag is turned on by default, regardless of the configuration settings.
When the file reaches 128 kilobytes (KB), it is renamed and compressed.
For op scripts, you can only customize tracing operations for
local op scripts. For remote op scripts (op scripts executed using
the op url
command), Junos OS always logs the default trace
events in the default op script log file.
Options
file 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 cscript.log, op script process
tracing is placed in the file op-script.log, and SNMP script tracing is placed in the file snmp.log. If you include the
|
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. When 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 number of files, you also must specify
a maximum file size with the
|
flag flag | Tracing operation to perform. The
|
no-world-readable | Restrict file access to owner. This is the default. |
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 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
|
world-readable | Enable unrestricted file access. |
Required Privilege Level
maintenance—To view or add this statement in the configuration.
Release Information
Statement introduced in Junos OS Release 7.4.