Lists server process or kernel event sets and their states
Synopsis
dfstrace lsset [-set set_name...] [-cdsentry server_entry_in_CDS] [-help]
Options
-set set_name
Specifies the name of each event set you want to list. Omit this option to list all kernel event sets on the local machine or all server process event
sets for the server process specified with the -cdsentry option.
-cdsentry server_entry_in_CDS
Specifies the full DCE path name (/.:/hosts/machine/process_name) of a server process whose event sets
you want to list. Use this option with the -set option to list a distinct group of server process event sets; use this option alone to list all event sets associated with the server
process. Omit this option to list kernel event sets.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
Description
The dfstrace lsset command lists the specified server process or kernel event sets and their states. If you want to list a kernel event set, it must reside
on the local machine. If you want to list a server process event set, it can reside on any machine; however, you must use the -cdsentry option to specify the appropriate server process.
To list a specific event set, identify the event set with the -set option. Use the -cdsentry option to list a specific server process event set, omit that option to list a specific kernel event set.
To list all kernel event sets on a machine, run the dfstrace lsset command without any options. To list all server process event sets associated with a particular server process, run the command with the -cdsentry option only.
Privilege Required
To list a kernel event set, the issuer must be logged in as root on the local machine. To list a server process event set, the issuer must be listed
in the admin list associated with that process on the machine specified with the -cdsentry option (for example, admin.fl for the flserver process and
admin.ft for the ftserver process).
Output
The command lists each event set and its state. There are three event set states:
· active - Tracing is enabled for the event set.
· inactive - Tracing is temporarily disabled for the event set; however, the event set continues to claim space occupied by the logs to which it sends data.
· dormant - Tracing is disabled for the event set; furthermore, the event set releases its claim to space occupied by the logs to which it sends data. When all of the event sets that send data to a particular log are in this state, the space allocated for that log is freed.
An event set can also be persistent. If an event set is persistent, its state cannot be set during a global state setting (executed by issuing dfstrace setset command with the -set option). Of course, the event set's state can still be set if the event set is otherwise specified with the dfstrace setset command. The persistent attribute prevents accidental resetting of an event set's state. The attribute is assigned to an event set when the kernel or server process is compiled and cannot be changed.
Examples
The following command lists all kernel event sets and their states on the local machine:
# dfstrace lss
Available sets:
cm: active
fx: active
fshost: active
xops: active
episode/anode: dormant
episode/logbuf: dormant
episode/vnops: dormant
tkc: inactive
tpq: active
tkm: active
The following command lists state information on the event set ubikvote for the flserver process on the machine dewitt:
$ dfstrace lss -set ubikvote -cdsentry /.:/hosts/dewitt/flserver
ubikvote: active
Related Information
Commands: dfstrace clear(8dfs)