Solaris system startup and shutdown

Hi all,

Solaris 2.x systems using UNIX-based System V Release 4.0 standards and flexible boot process, making it easy to generate and customize the various hosts and systems are common startup and shutdown process, which is used by Solaris 1.x simple BSD style network startup process contrasts, which is the lack of state of the system for different startup scripts of different organizational forms. I want to know that some basic terms and initialization parameters into the Solaris system that is in single-user and multi-user run level. Please reply. Thanks in advance.

In many ways, Solaris start-up and shutdown in many other systems have similarities, however, awareness and understanding of Solaris operating system, different characteristics to other servers is also very important. SPARC hardware is known as an important function of OpenBoot firmware surveillance system, which is responsible for some of the important tasks before the start:
# Start by typing the following characters in Solaris Operating System:
ok boot
At the OpenBoot prompt, it will start the Solaris kernel (on Solaris x86 on, boot order must be adopted by Primary Boot Subsystem menu execution).
# Set system configuration parameters, such as the boot device, it can be one of several hard drives (from the device to determine the full path name), or on the network one other host, it can be a CD-ROM drive.
#Through the implementation of the following clause in order to monitor network traffic:
ok watch-net

Many Linux versions of LILO Linux loader with a different, OpenBoot is not just a simple operating system loader, it also allows to start the process began before the write, load and run with the stack-based Forth programming language written in procedure, when customized for a large enterprise server, often require the company's logo displayed at startup, rather than the default Sun logo, then, OpenBoot, this feature is very useful, and can generate a composition with the appropriate pixel The Forth array, and then run the oem-logo command. In addition, single-user and multi-user init state, you can also start after setting the value of variables, which can be run as super user eeprom command to achieve. For example, the eeprom Can be used to start self-test of the RAM into a 64M:
server # eeprom selftest-# megs = 64
Check and reply.

The important feature is the adoption of efficient design of kernel and user program mode to achieve the purpose of maximizing up-time. In some non-Solaris server environment, each time to install a new application must be re-starting system, or need to re-configure the kernel. On Solaris systems, only in rare circumstances when the need to reboot the system, because the application from the logic and system configuration options are separated, and many system-level configuration options can be set up super-user shell, For example, many TCP / IP option can use the following command dodo mdifications:
server # ndd / dev / tcp

From the OpenBoot starts, Solaris there are several different modes of operation, known as the "run level" or "init state", the reason for so called because the commonly used init command to change the run level, of course, can also use the init-wrapper script (such as the shutdown). The init state can be a single user can also be a multi-user, often for each state represents a different management purpose, and is completely unrelated (that is, a system at any time only one init state above). Typically, a boot designed to take from time to time Solaris system will complete a series of predefined steps to start for the provision of basic system services, the main customer service and optional services, all of the necessary application software programs. Check and reply.

The Solaris installation process for administrators to automatically generate a run control script, however, if you want to install third-party software (such as a database server), you'll need in the / etc / init.d directory, generate your own run control script in order to be able to automatically load when the system starts these services. If for some reason (for example, loss of regular power supply) systems need to power off or switch to a particular mode of management to perform diagnostic tests can also be based on a series of pre-defined control script to kill the various services and to save user data. All the best.