Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Administration: Common Tasks Oracle Solaris 11 Information Library |
1. Locating Information About Oracle Solaris Commands
2. Managing User Accounts and Groups (Overview)
3. Managing User Accounts and Groups (Tasks)
4. Booting and Shutting Down an Oracle Solaris System
What's New in Booting and Shutting Down a System?
Support for Administratively Provided driver.conf Files
Boot and Shutdown Progress Animation
x86: Removal of Support for 32-Bit Kernel
Booting and Shutting Down an Oracle Solaris System (Overview)
Management of Boot Services by the Service Management Facility
Booting a System to a Specified State (Task Map)
Booting a System to a Specified State (Run Level)
Determining a System's Current Run Level
SPARC: How to Boot a System to a Multiuser State (Run Level 3)
x86: How to Boot a System to a Single-User State (Run Level S)
Shutting Down a System (Task Map)
How to Shut Down a System by Using the shutdown Command
Bringing a System to a Shutdown State (Run Level 0) by Using the init Command
Booting a System From the Network
Accelerating the Reboot Process (Task Map)
Accelerating the Reboot Process
How to Initiate a Fast Reboot of a SPARC Based System
How to Initiate a Fast Reboot of an x86 Based System
Changing the Default Behavior of the Fast Reboot Feature
Initiating a Standard Reboot of a System That Has Fast Reboot Enabled
Booting From a ZFS Boot Environment (Task Map)
SPARC: Booting From a ZFS Boot Environment
SPARC: How to Display a List of Available Boot Environments During the Boot Sequence
SPARC: How to Boot From a ZFS Boot Environment or Root File System
Modifying Boot Parameters (Task Map)
SPARC: How to Determine the Default Boot Device
SPARC: How to Change the Default Boot Device by Using the Boot PROM
x86: How to Modify Boot Parameters by Using the eeprom Command
x86: How to Modify Boot Parameters at Boot Time
Adding a Linux Entry to the GRUB Menu After an Installation
Keeping a System Bootable (Task Map)
Determining Whether the boot-archive SMF Service Is Running
How to Clear a Failed Automatic Boot Archive Update by Manually Updating the Boot Archive
x86: How to Clear a Failed Automatic Boot Archive Update by Using the auto-reboot-safe Property
Where to Find More Information About Booting and Shutting Down a System
5. Working With Oracle Configuration Manager
6. Managing Services (Overview)
9. Managing System Information (Tasks)
10. Managing System Processes (Tasks)
11. Monitoring System Performance (Tasks)
12. Managing Software Packages (Tasks)
14. Scheduling System Tasks (Tasks)
15. Setting Up and Administering Printers by Using CUPS (Tasks)
16. Managing the System Console, Terminal Devices, and Power Services (Tasks)
17. Managing System Crash Information (Tasks)
18. Managing Core Files (Tasks)
19. Troubleshooting System and Software Problems (Tasks)
20. Troubleshooting Miscellaneous System and Software Problems (Tasks)
Oracle Solaris is designed to run continuously so that the electronic mail and network software can work correctly. However, some system administration tasks and emergency situations require that the system be shut down to a level where it is safe to remove power. In some cases, the system needs to be brought to an intermediate level, where not all system services are available.
Such cases include the following:
Adding or removing hardware
Preparing for an expected power outage
Performing file system maintenance, such as a backup
For information about using your system's power management features, see the poweradm(1M) man page.
For detailed information when to shutdown a system and which commands to use, see System Shutdown Commands in Booting and Shutting Down Oracle Solaris on SPARC Platforms.
# who
# shutdown -iinit-state -ggrace-period -y
Brings the system to an init state that is different from the default of S. The choices are 0, 1, 2, 5, and 6.
Run levels 0 and 5 are states reserved for shutting the system down. Run level 6 reboots the system. Run level 2 is available as a multiuser operating state.
Indicates a time (in seconds) before the system is shut down. The default is 60 seconds.
Continues to shut down the system without intervention. Otherwise, you are prompted to continue the shutdown process after 60 seconds.
For more information, see the shutdown(1M) man page.
Do you want to continue? (y or n): y
If you used the shutdown -y command, you will not be prompted to continue.
Type Ctrl-d to proceed with normal startup, (or give root password for system maintenance): xxxxxx
Example 4-3 SPARC: Bringing a System to a Shutdown State (Run Level 0) by Using the shutdown Command
In the following example, the shutdown command is used to bring a SPARC based system to run level 0 in five minutes without requiring additional confirmation.
# who root console Jun 17 12:39 userabc pts/4 Jun 17 12:39 (:0.0) # shutdown -i0 -g300 -y Shutdown started. Thu Jun 17 12:40:25... Broadcast Message from root (console) on pretend Thu Jun 17 12:40:25... The system pretend will be shut down in 5 minutes . . . Changing to init state 0 - please wait # INIT: New run level: 0 The system is coming down. Please wait. System services are now being stopped. . . . The system is down. syncing file systems... done Program terminated Type help for more information ok
See Also
Regardless of why you shut down a system, you will probably want to return to run level 3, where all file resources are available, and users can log in. For instructions on bringing a system back to a multiuser state, SPARC: How to Boot a System to a Multiuser State (Run Level 3).
Run levels 0, 5, and 6 are reserved for shutting down a system. Bringing a system to run level 0 enables power to the system to be safely turned off. As shown in the example that follows, the init command is used to bring a system to run level 0.
Use this procedure when you need to shut down a stand-alone system.
# init 5
For more information, see the init(1M) man page.
Example 4-4 Bringing a System to the Shutdown State (Run Level 0) by Using the init Command
In the following example, the init command is used to bring a system to the level where it is safe to turn off power:
# init 0 # INIT: New run level: 0 The system is coming down. Please wait. . . . The system is down. syncing file systems... [11] [10] [3] done Press any key to reboot