Skip to ContentSun and Oracle Channel Sun How to Buy Log In

Solaris Handbook for SMCC Peripherals

内に含ま

その他のドキュメント

サポートリソース

PDF 文書ファイルをダウンロードする

CHAPTER 1

Before You Start

This chapter describes the requirements and procedures that you must perform to power off or shut down your system.

This chapter contains the following information:

*Requirements* you must perform	*page 1*
Verifying which release of the SunOS you are currently running	*page 2*
The `init`, `shutdown`, `halt`, and `reboot` commands	*page 3*
A closer look at the `init` command	*page 4*
*Shutting Down a Single-User System Using init*	*page 5*
*Shutting Down a Multiuser System Using shutdown*	*page 8*

Requirements

Before you set up a peripheral device, you must:

Turn on the power to the system.
Install the Solaris software.

Note - This manual does not describe how to install the Solaris operating environment.

Tip - For Solaris installation instructions, refer to the Solaris Advanced Installation Guide documentation.

Verifying the System Environment

Verify the system environment that is installed on your system before you install a peripheral device.

· Type uname -rs and press Return.

The operating system responds by displaying the following message:


  SunOS 5.x

The screen should display the SunOS version of the operating system. The Solaris system environment, to which this manual refers, includes the SunOS operating system as well as compilers and other software.

TABLE 1-1 shows the SunOS releases shipped with the corresponding Solaris releases.

TABLE 1-1

If you are running the following SunOS:	You are using the following Solaris system environment:
SunOS 5.0	Solaris 2.0
SunOS 5.1	Solaris 2.1
SunOS 5.2	Solaris 2.2
SunOS 5.3	Solaris 2.3
SunOS 5.4	Solaris 2.4
SunOS 5.5	Solaris 2.5
SunOS 5.5.1	Solaris 2.5.1
SunOS 5.6	Solaris 2.6

Note - If you are working in an environment other than Solaris 2.x, the commands and tasks described in this manual do not apply.

Tip - If you are using SunOS 4.x, refer to the Solaris 1.x (SunOS 4.x) Handbook for SMCC Peripherals.

Shutting Down the System

Power off or shut down your system before you install a peripheral device.

When preparing to shut down a system, you need to determine which of the following shutdown commands is appropriate for the system and the task at hand:

· /sbin/init
· /usr/sbin/shutdown
· /usr/sbin/halt
· /usr/sbin/reboot

Tip - See TABLE 1-2 on page 4 for a definition of each shutdown command

These commands initiate shutdown procedures, kill all running processes, write data to disk, and shut down the system software to the appropriate run level.

Note - init and shutdown are the two most reliable ways to shut down a system because they use rc scripts to kill running processes and shut down the system with minimal data loss. The halt and reboot commands do not run the rc scripts properly and are not the preferred method for shutting down the system.

Tip - For more information about rc scripts, see chapter 10 of the System Administration Guide, "Boot Files and Run Levels."

TABLE 1-2 describes each of the shutdown commands. The sections that follow provide more details about the init and shutdown commands as they apply to the Solaris operating environment.

TABLE 1-2

Command	Function
`init`	Use the `init` command to shut down a single-user system or to change its run level. You can use `init` to place the system in power-down state (`init 0`) or into single-user state (`init 1`).
`shutdown`	Use the `shutdown` command when shutting down a system with multiple users. The `shutdown` command sends a warning message to all users who are logged in, waits for 60 seconds (the default), and then shuts down the system to single-user state.
`halt`	Use the `halt` command when the system must be stopped immediately and it is acceptable *not* to warn any current users. The `halt` command shuts down the system without any delay. It does not warn any other users on the system.
`reboot`	Use the `reboot` command to shut down a single-user system and bring it into multiuser state. `reboot` does not warn other users on the system.

The `init` Command

Use the init command to shut down single-user systems and keep the system running correctly. In addition, use the init command to change init states. You can also specify the init state as an argument to the shutdown command with the -i option.

The init state in which the system is running defines what services and resources are available to users. A system can run in only one init state at a time. There are four types of init states.

Power-down (run level 0)
Single-user (run levels 1 and s or S)
Multiuser (run levels 2 and 3)
Reboot (run levels 5 and 6)

Tip - See TABLE 1-3 on page 5 for a description of the various init states.

TABLE 1-3 init

`init` State	Run Level	Function
Power-down state	0	Shuts down the system so that it is safe to turn off the power.
System administrator state	1	Lets you perform administrative tasks on systems requiring only single user access. `/` and `/usr` are the only file systems mounted, and you can access only minimum kernel utilities. The terminal from which you issue this command becomes the console. No other users are logged in.
Multiuser state	2	Gives multiple users access to the system and the entire file system. All daemons run except the NFS server and `syslog`.
Remote resource-sharing state	3	Lets you perform normal operations with NFS resource-sharing available.
Alternative multiuser state	4	Provides no function at this time.
Interactive reboot state	5	Prompts you for a device other than the default boot devices. You can also change to this level by using the `reboot -a` command.
Reboot state	6	Shuts down the system to run level 0, and then reboots to multiuser level (the default level in the `inittab` file).
Single-user state	s or S	Runs the system as a single user with all file systems mounted and accessible.

· Shutting Down a Single-User System Using `init`

This section describes how to shut down a single-user system.

Become superuser.
Add a device driver, if necessary.
If a new device driver is required, use the pkgadd command and the Software Manager tool to perform this task.
Tip - Refer to the System Administration Guide and the Solaris Advanced Installation Guide manual for instructions on adding a device driver.

Note - This task is optional; most device drivers are already part of the operating system. If a device driver is required, you would typically find a CD-ROM with the drive, as well as instructions on how to add the device driver. If you cannot find a CD-ROM or instructions on how to add a specific device driver, a new device driver is probably not needed. Therefore, you can skip this step.

Ensure that the operating system checks for the presence of any newly installed peripheral devices when you power on or reboot your system.


  # touch /reconfigure

Note - The touch /reconfigure command performs the same function
as the boot -r command. It allows the operating system to
recognize the presence of all newly installed peripheral
devices.

Tip - For information on booting your system in different modes, see Appendix A, "."

Change to the root directory.


  # cd /

Shut down the system.


  # init 0

This command writes data to the disk, kills all active processes, brings the system down to power-down state, and displays the ok prompt.

If you are asked for confirmation, type y.


  ok Do you want to continue? (y or n): y

Note - Be sure that you turned on all SCSI devices, such as disk and tape drives, before you attempt to use the probe-scsi or probe-scsi-all commands. The operating system can detect connected SCSI devices only if you turned them on.

Reset the SCSI bus and kill all running processes by typing:


  ok reset  
  Immediately press <Stop-a>

Note - This interrupts the reboot process and clears all SCSI bus activity to ensure an effective probe-scsi or probe-scsi-all search.

List the SCSI target IDs that are currently being used on the Host SCSI bus by typing:


  ok probe-scsi

If you have more than one host bus on your system, use the probe-scsi-all command because it probes for all SCSI devices on every SCSI bus including the host bus.

Choose an unused SCSI target ID for your device.
Note the target IDs that are already assigned and choose an unused target ID to set the SCSI switch or jumpers on your peripheral device.

After the ok prompt is displayed, turn off the power to the system and then to all external peripheral devices.
You are now ready to install the peripheral device. Refer to the documentation that accompanies your hardware, and the appropriate section in this manual:

*Adding a Disk Drive*	*page 16*
*Adding a Tape Drive*	*page 29*
*Adding a CD-ROM Drive*	*page 40*
*Adding an Additional CD-ROM Drive*	*page 41*
*Adding a Diskette Drive*	*page 42*

The `shutdown` Command

Use the shutdown command to shut down servers when users must be notified of the impending shut down.

· Shutting Down a Multiuser System Using `shutdown`

This section describes how to shut down a multiuser system, such as a server.

Become superuser.
To find out if users are logged into the system, type:


  # who

A list of all logged-in users is displayed. You can send mail or broadcast a message to let users know that the system is being shut down.

Add a device driver, if necessary.
If a new device driver is needed, use the pkgadd command and the Software Manager tool to perform this task.
Tip - Refer to the System Administration Guide manual and the Solaris Advanced Installation Guide manual for instructions on adding a device driver.
Note - This task is optional; most device drivers are already part of the operating system. If a device driver is required, you would typically find a CD-ROM with the drive as well as instructions on how to add the device driver. If you cannot find a CD-ROM or instructions on how to add a specific device driver, a new device driver is probably not needed. Therefore, you can skip this step.
Ensure that the operating system checks for newly installed peripheral devices when you power on or reboot your system, type:


  # touch /reconfigure

Note - The touch /reconfigure command performs the same function
as the boot -r command. It allows the operating system to
recognize the presence of all newly installed peripheral
devices.

Tip - For information on booting your system in different modes, see Appendix A, "Booting Your System."

Change to the root directory, by typing:


  # cd /

Shut down the system, by typing:


  # shutdown -y -g30 -i0

In this command,

shutdown

Brings a system to run level s (single-user mode) by default. A message is broadcast to all users. After a 60-second wait (default), you are asked to confirm that you want to shut down the system.

-y

Continues to shut down the system without intervention; otherwise, you are prompted to continue the shutdown process.

-g grace-period

Indicates a time (in seconds) before the system is shut down. The default is 60 seconds.

-i init-state

Allows you to bring the system to an init state that is different from the default of 2. (Refer to TABLE 1-3 on page 5 for init state information.)

In the following example, the system will be brought to run level 0 in 3 minutes without requiring additional confirmation.


  # shutdown -y -g180 -i0  
  Shutdown started.    Fri Nov 4 11:07:33 MST 1994  
  Broadcast Message from root (console) on pluto Fri Nov 4 11:07:34  
  The system will be shut down in 3 minutes  
                      .  
                      .  
                      .  
  INIT: New run level: 0  
  The system is coming down. Please wait.  
                      .  
                      .  
                      .  
  The system is down.  
  syncing file systems... [11] [9] [5] done  
  Program terminated  
  Type help for more information  
  ok

If you are asked for confirmation, type y.


  ok Do you want to continue? (y or n): y

Reset the SCSI bus and kill all running processes, by typing:


  ok reset  
  Immediately press <Stop-a>

Note - This interrupts the reboot process and clears all SCSI bus activity to ensure an effective probe-scsi or probe-scsi-all search.

List the SCSI target IDs that are currently being used by typing:


  ok probe-scsi

If you have more than one host bus on your system, use the probe-scsi-all command because it probes for all SCSI devices on every SCSI bus including the host bus

Note - probe-scsi-all will not see devices connected with a Soc/S adapter board, such as a SPARCstorage Array.

Choose an unused SCSI target ID for your device.
Note the target IDs that are already assigned and choose an unused target ID to set the SCSI switch or jumpers on your peripheral device.

Turn off the power to the system and then to all external peripheral devices after the ok prompt is displayed.
You are now ready to install your peripheral device. Refer to the documentation that accompanies your hardware, and the appropriate
section in this manual:

*Adding a Disk Drive*	*page 16*
*Adding a Tape Drive*	*page 29*
*Adding a CD-ROM Drive*	*page 40*
*Adding an Additional CD-ROM Drive*	*page 41*
*Adding a Diskette Drive*	*page 42*

内に含ま

その他のドキュメント

サポート リソース

Before You Start

Requirements

Verifying the System Environment

Shutting Down the System

The init Command

· Shutting Down a Single-User System Using init

The shutdown Command

· Shutting Down a Multiuser System Using shutdown

サポートリソース

The `init` Command

· Shutting Down a Single-User System Using `init`

The `shutdown` Command

· Shutting Down a Multiuser System Using `shutdown`