DataMuseum.dk

top - metrics - download

    Length: 3579 (0xdfb)
    Types: TextFile
    Names: »READ_ME«

└─⟦180fe333a⟧ Bits:30000405 8mm tape, Rational 1000, SW CATALOG, 10_20_0
└─⟦180fe333a⟧ Bits:30000537 8mm tape, Rational 1000, SW Catalog 10_20_0
    └─⟦5cb1d1d7f⟧ »DATA« 
        └─⟦3b1ee7bd8⟧ 
            └─⟦this⟧ 

TextFile

                      Reboot Server revision 804-1
                      ----------------------------




Overview
--------

Package Reboot_Server with its associated units Context, Logfile_Library
and Start_Reboot_Server is a tool used to auto-reboot the R1000 on a
regular basis. (Rational Customer Support Center recommends once a week).



Installation
------------

Ensure that group System has Read/Write access to the location you have chosen.

Edit the function body of Context to reflect this location.

Edit the function body of Logfile_Library to reflect where you want the
logfiles generated by this tool to be stored. (!Machine.Error_Logs is the
default location).

Promote all of the units to the promoted state.

Add a link for Start_Reboot_Server to !Machine and edit Initialize_Site'Body
to include a call to Start_Reboot_Server.

Set the Operator Mode Keyswitch located at the System Control Panel to
the Interactive position.

Shut down the system in an orderly fashion. This is to ensure that a snap
shot is taken.

Change the BOOT/CRASH/MAINTENANCE options to enable R1000 Auto boot.

Boot the system.

Set the Operator Mode Keyswitch located at the System Control Panel to
the Automatic position.

After the system has completed the boot sequence, wait for 15 minutes to
allow the Reboot Server server to become active. (This is done to prevent
a disaster if the server runs amok). Use the commands in package Reboot_Server
to update the server to reflect your needs.



Description
-----------

After system boot a server job named Reboot_Server is created. This server
utilises two pipes, Input and Output, for communiction with the surrounding
world and a binary file named Data to store permanent information. These
objects are automatically created the first time the server is activated.
At every system boot a logfile with a name of the form
Reboot_Server_Log_yy_mm_dd_at_hh_mm_ss is generated at the location
specified in Logfile_Library.

The server keeps a record containing information such as which weekday(s) and
what time to reboot the system. This information can easily be changed using
the commands in package Reboot_Server.

Currently supported commands are:

    Cancel_Next -- to cancel the next, by Reboot Server, scheduled reboot.
    Change_Day  -- to change target weekday(s) for reboot.
    Change_Time -- to change Shutdown and Deadline times for reboot.
    Kill        -- to terminate the Reboot Server server.
    Status      -- to obtain status from the Reboot Server server.

The command Change_Day selects one or more target weekdays at which a reboot
should occur. Change_Time sets the two times specified as Shutdown and
Deadline which constitutes a time frame which the start of a reboot has to
occur within. The reason for such a time frame is that in case the disk daemon
is active, the Reboot Server will wait for its completion or the occurance of
the time specified as Deadline. In a case where the deadline is hit, the reboot
is cancelled. It is assumed that Shutdown is less than Deadline.

Every 4 seconds the Reboot Server checks the input pipe for any incoming
messages (commands given by a user) and compares time and weekday for the
next reboot with the actual time. If a message is sent to the server, the
server will immediately execute the requested command and send a status
message back to the requestor. The same status message will also be written
to the logfile.

At reboot time the server will schedule a shutdown, close all open
objects and terminate itself. Within 2 minutes the system is shut down.