Configuring your system for unattended reboots

To obtain the unattended reboot functionality on your system, you will need to complete the following steps:

1. Change the values of the PANICBOOT and TIME system parameters.

   It is good practice to use the System Defaults Manager in SCOadmin or the defadm(1M) command to change the values of system parameters.

   Parameter	Defined in file	Default value	Value needed to obtain unattended reboot functionality
   PANICBOOT	/etc/default/init	NO	YES
   TIME	/etc/default/dump	-1	either 0 (zero) or a positive number

   When PANICBOOT is set to YES, a memory dump is created (in either the dump slice or the primary swap device) following a system panic, and the system automatically reboots. The new value of PANICBOOT does not take effect until the next time you reboot the system.

   When the system comes back up after a panic, /sbin/dumpcheck will see if a dump is present and decide whether or not to issue a prompt by looking at /etc/default/dump. If TIME is set to zero, prompts about saving the dump are never asked at the console. If TIME is set to a positive number of seconds, the system asks whether to save the dump, waits TIME number of seconds, then continues to reboot. If TIME is not defined, or is a negative number, the system asks whether to save the dump and waits forever for a response.

2. If you have the kernel debugger, kdb(1M), installed and loaded at the time of a panic, the kernel will enter the debugger rather than proceeding immediately to dump and reboot. To prevent this, you must ensure that kdb is not loaded.

   Edit the file /etc/conf/sdevice.d/kdb and remove the line that says

      $static
   

   Then rebuild the kernel using the following command:

      /etc/conf/bin/idbuild -B
   

   An alternative to this step is to uninstall kdb.

3. Reboot the system.