Performing a Sane Shutdown
 Karl Pearson
 Updated 1/17/97
The following check-list, though certainly not exhaustive, gives a general outline for performing a sane shutdown preparatory to system maintenance or the coming of bad weather which could damage the equipment.
  1. Check LIST-READU EVERY, at TCL in uniVerse account to verify the absense of file locks. When file locks are gone (use UNLOCK ALL to forcibly remove them if necessary), log all users off (they should log off each day before leaving work) using MASTER OFF ALL from TCL in the uniVerse account.
  2. Stop all uniVerse processes. Don't forget "sleeping" processes such as Day End. NOTE: Performing a backup before a shutdown insures a valid "snapshot" of the system in the cases where the system might not come back up.
  3. Perform the desired shutdown option:
    1. Execute the command: shutdown -r now (the command reboot may also work) at the # prompt in root. The system should come back up normally if this option is used. This is all that is needed if the system isn't being taken down for maintenance or to prevent damage during storms.
    2. Execute the command: shutdown -h now at the # prompt in root (the / directory). This option is usually only used when it is desired to turn off all power to a system.
  4. If 3.2 is selected, the process for powering down a system when the console shows a statement indicating that the shutdown is complete, should be performed in the following order:
    1. Turn the main system power off.
    2. Turn the console off.
    3. Turn the printers off.
    4. Turn other external peripherals off, ie: tape drives, external disks, connected expansion cabinets, network controllers, etc. The order after the system is not as critical as when powering back up.
    5. If the shutdown is being performed because of an approaching storm, be sure to disconnect the phone lines that connect to modems.
  5. After the system maintenance requiring power-off status is completed (or the storm has passed), the order of powering back up is:
    1. Reconnect phone lines to modems.
    2. Turn external peripherals on, ie: network controllers, expansion cabinets, external disks and tape drives.
    3. Turn printers on.
    4. Turn console on.
    5. Turn the main system power on after all other devices have finished their POST (power-on self test). Some of the peripheral devices don't have to do any processing. Notable exceptions: laser printers, tape drives, expansion cabinets that contain disks, tape drives, etc.
At this point, and barring any damaged parts, the system should come up normally.