- traceoptions {
- file filename <files number> <size size>;
- flag flag;
- }
- [edit system scripts commit]
Statement introduced in JUNOS Release 7.4.
Define tracing operations for commit scripts.
If you do not include this statement, no commit-script-specific tracing operations are performed.
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. If you include the file statement, you must specify a filename. To retain the default, you can specify cscript.log 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 trace-file.0, then trace-file.1, 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.
flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:
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 trace-file.0. When trace-file again reaches its maximum size, trace-file.0 is renamed trace-file.1 and trace-file is renamed trace-file.0. 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.
See Tracing Commit Script Processing.
maintenance—To view this
statement in the configuration.
maintenance-control—To
add this statement to the configuration.