test

Sun Remote System Control (RSC) User's Guide

RSC View Log Commands

Use the following RSC commands to work with RSC and console log files:

loghistory [index [+|-]n] [pause n]

Use the loghistory command without subcommands to display the history of all events logged in the RSC event buffer. These events include server reset events and all RSC commands that change the state of the system. You can also use the command abbreviation lhist.

Use the following subcommands to control loghistory display.

index [+|-]n

Use the index subcommand to designate a buffer position at which to begin the display, as follows:

The origin of counting is 1; that is, index +1 indicates the first line in the buffer, index -1 indicates the last. For example: 

rsc> loghistory index -30

This command prints the last 30 lines and any additional lines that were appended to the buffer between the time that the command began execution and the time that it terminated.

pause n

Use the pause subcommand to display n lines of the log at a time (similar to the more command). The value of n must be a decimal integer. The default is to display the entire RSC log without pausing.

Each event recorded in the log has the following format: 

$TIME $HOSTNAME $EVENTID $message

EVENTID is a unique identifier for the event, TIME is the time the event occurred (as measured by RSC time), and message is a user-friendly description of the event.

The following is an example event log entry: 

FRI JAN 01 07:33:03 1999 sst4828: 00060003: "RSC System booted"

consolehistory [boot|run|oboot|orun] [index [+|-]n] [pause n]

Use the consolehistory command to display console messages logged in RSC buffers. With no arguments, this command prints the entire contents of all non-empty console buffers. You can use the command abbreviation chist.

There are four console logs:

The boot and oboot buffers can contain up to 8 Kbytes of information, and the run and orun buffers can contain up to 16 Kbytes of information.

When the first power-on boot begins, RSC fills the original boot (oboot) buffer with data from the server's console. After that buffer fills up, it writes data to the original run (orun) log. When the orun log fills up, it overwrites old data in the orun log.

When RSC senses a server reset while in the orun log, it switches to the boot log. After that fills up, it switches to the run log. When the run log fills up, it overwrites old data in the run log.

When RSC senses a server reset while in the current run log, it switches to the current boot log again.

pause n

Use the pause subcommand to display n lines of the log at a time (similar to the more command). The value of n must be a decimal integer. The default is to display 10 lines of the log at a time.

See "loghistory [index [+|-]n] [pause n]" for a description of the index subcommand.

Note -

Time stamps recorded in console logs reflect server time. These time stamps may be offset from RSC time stamps recorded in the RSC event log. To find information on synchronizing RSC time with server time using the rscadm utility, see "date [-s] date [[mmdd]HHMM|mmddHHMM[cc]yy]][.SS]".

consolerestart

Use the consolerestart command to make the current boot and run logs the "original" logs (designated oboot and orun). This command copies the current boot and run buffers to the oboot and orun buffers, overwriting the previous contents. Then it clears the current boot and run buffers. You must have A level user permission to use this command.

After adding a hardware component to the server, reboot the server and then use the consolerestart command so that the new part will appear in the original console logs.