JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Basic Administration     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


1.  Managing User Accounts and Groups (Overview)

2.  Managing User Accounts and Groups (Tasks)

3.  Introduction to Shutting Down and Booting a System

What's New in Shutting Down and Booting a System

Support for Fast Reboot on the SPARC Platform

Automatic Boot Archive Recovery

GNOME Restart Dialog Support for Fast Reboot

Support for Fast Reboot on the x86 Platform

iSCSI Boot

Where to Find Shut Down and Boot Tasks

Shut Down and Boot Terminology

Guidelines for Shutting Down a System

Guidelines for Booting a System

When to Shut Down a System

When to Boot a System

4.  Shutting Down and Booting a System (Overview)

5.  Shutting Down a System (Tasks)

6.  Modifying Oracle Solaris Boot Behavior (Tasks)

7.  Booting an Oracle Solaris System (Tasks)

8.  Troubleshooting Booting an Oracle Solaris System (Tasks)

9.  Managing the Oracle Solaris Boot Archives (Tasks)

10.  x86: GRUB Based Booting (Reference)

11.  Managing Services (Overview)

12.  Managing Services (Tasks)


When to Shut Down a System

The following table lists system administration tasks and the type of shutdown method that is required to initiate the task.

Table 3-1 Shutting Down a System

Reason for System Shutdown
Appropriate Run Level
For More Information
To turn off system power due to anticipated power outage.
Run level 0, where it is safe to turn off power
To change kernel parameters in the /etc/system file.
Run level 6 (reboot the system)
To perform file system maintenance, such as backing up or restoring system data.
Run level S (single-user level)
To repair a system configuration file such as /etc/system.
To add or remove hardware from the system.
Reconfiguration boot (shut down and turn off power when adding or removing devices, if the devices are not hot-pluggable)
To repair an important system file that is causing system boot failure.
To boot the kernel debugger (kmdb) to track down a system problem.
Run level 0, if possible
To recover from a hung system and force a crash dump.
Reboot the system by using the kernel debugger (kmdb), if the debugger can't be loaded at runtime.
Run level 6 (reboot the system)

For examples of shutting down a server or a stand-alone system, see Chapter 5, Shutting Down a System (Tasks).