traceoptions (Resource Cleanup)

Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. To include the file statement, you must specify a filename.

(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.

Specify which tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:

• all—Enable all trace options flags.

• events—Trace process state change and cleanup events.

• gencfg——Trace GENCFG blobs recorded for cleanup.

• module—Trace module code.

• sysvsem—Trace SYSV semaphores recorded for cleanup.

• sysvshm—Trace SYSV shared memory segments recorded for cleanup.

• tracking—Trace tracking code.

• ui—Trace user interface operations.

Specify the level of debugging output:

• all—Match all levels.

• error—Match error conditions.

• info—Match informational messages.

• notice—Match conditions that warrant special handling (but are not errors).

• verbose—Match verbose messages.

• warning—Match warning messages.

(Optional) Refine the output to include lines that contain the regular expression.

Disable remote tracing.

(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). If you specify a maximum file size, you also must specify a maximum number of trace files with the files number option.

(Optional). Grant all users permission to read log files, or restrict the permission only to the root user and users who have the Junos maintenance permission.