
Using Technician Interface Software
6-8
Example (log -w)
#1: 08/13/95 16:32:20.011 INFO SLOT 2 GAME Code:11 Starting image int/9.00/52 Mon Jul 31 22:20:19 EDT
#2: 08/13/95 16:32:21.031 INFO SLOT 2 GAME Code:9 BackBone 0 became re-connected
#3: 08/13/95 16:32:21.511 INFO SLOT 2 GAME Code:10 slot 4 became re-connected
#4: 08/13/95 16:32:21.554 INFO SLOT 2 GAME Code:10 slot 3 became re-connected
#5: 08/13/95 16:32:29.238 INFO SLOT 2 NVFS Code:42 Volume 2: Service initializing.
#6: 08/13/95 16:32:33.347 INFO SLOT 2 MIB Code:4 Using configuration file '2:config'
#7: 08/13/95 16:32:33.480 INFO SLOT 2 MIB Code:3 Service initializing.
Saving the Events Log
You can save the events in the current event buffer to a file for later retrieval.
Enter the following.
save log
<vol>
:
<log_file>
<vol> is the volume on which to store the file
<log_file> is the name of the file you are creating to store the events.
We recommend that you use the .log file extension when creating log files.
You can verify that the log file is saved by entering the
dir <vol>: command.
You can use the same optional arguments when displaying a log file you
previously saved, as you can to display a current log (refer to the section that
follows for instructions).
Another option is to limit the event types you save to a log file. When you display
the log file after saving it, only those event types you saved are displayed. Enter
the following command to limit the event types you save to a log file:
save log
<vol>
:
<log_file>
[-d
<date>
] [-t
<time>
] [-e
<entity>
] [-f
<severity>
]
[
-s
<slot_ID>
]
Refer to the previous section for a description of the optional arguments.
Caution: The system automatically overwrites any file on the volume that has
the same filename. To avoid overwriting an existing file, display a list of the
volume’s contents (with the
dir <vol>: command) and determine the filenames
already in use.
Komentáře k této Příručce