Professional Documents
Culture Documents
1. Booting of system made fast by starting independed process paralley unlike in solaris 9 process are started one after other which elapsed the boot tim 2. Automatic Service restarting. In solaris 9 we need to manually start service and all it dependencies whereas in Solaris 10 interdependencies are started automatically which make administration easy 3. In Solaris 10 all services are managed by svcs command whereas in solaris 9 need to find out from where we need to start the services. 4. SMF is a core part of the predictive self-healing technology available in the Solaris 10 OS, and it
provides automatic recovery from software and hardware failures as well as administrative errors
5. 6.
In addition, SMF-managed services can be delegated to non-root users. Finally, SMF is a follow-on to the legacy method of starting and stopping services, though /etc/rc scripts will continue to run when present for backward compatibility.
Top of Page
Top of Page
System administrators can more easily monitor services using Solaris Service Manager's service status information and service activation/deactivation interfaces based on the commands (svcs(1), svcadm(1) etc). Until Solaris 9, it was a complicated procedure to understand service status. Service level information was not provided and system administrators have to assume service status from their own analysis of kernel level information. A slow and error prone process.
svcadm(1M) command
Services and the services on which they depend are started in their appropriate order using the Solaris Service Manager svcadm(1) command. System administrators are longer required to run complicated service startup operations. For example, if there are two services, Service A and Service B, and Service A depends on Service B, previously the system administrator needed to start the services paying close attention to their dependent relationship. Now with Solaris10, they only have to start Service A. Solaris Service Manager automatically detects that Service B needs to be started, and starts the services in the right sequence.
With Solaris 10 the traditional service stop procedure using the kill(1) or pkill(1) commands is no longer available. This is because, once stopped, Solaris Service Manager will automatically restart them. So a new command, svcadm (1M) is now used for stopping services.
References
Solaris 9 or earlier versions ps(1) command (only process information is shown) Solaris 10
Service status
Service stop
# /etc/init.d/cron stop
(1)# /etc/init.d/cron stop (2)# mv /etc/rc2.d/S75cron /etc/rc2.d/_S75cron (Need to rename the service start script) (1) # /etc/init.d/cron stop (2) # /etc/init.d/cron start