<< Previous: Installing Sun Grid Engine Software Interactively

Next: Installing Sun Grid Engine Software Interactively

Sun Grid Engine Information Center
Installing Sun Grid Engine
Index

Installing SMF Services

The Service Management Facility (SMF) is a new feature in Solaris 10. It provides a unified model for controlling services, replaces RC scripts, handles service dependencies, provides better service availability, and speeds up boot process. If you do not use at least Version 10 of the Solaris OS in your cluster, or you do not plan to use SMF, continue with Installing Sun Grid Engine Software Interactively.

Note SMF is now the default for the hosts that run at least Version 10 of the Solaris OS. If you want to use the old behavior (RC files) for the Solaris hosts, you need to start the installation with the -nosmf option. Use the following command: ./inst_sge -x -nosmf

Installing SMF services includes the following topics:

Why Install SMF Services?

SMF provides a unified administrative model of the persistent services. It solves many challenges of the previous approaches. All services have a common place for log files. Persistent services are automatically restarted on failure. For more information, see SMF documentation.

Additional Setup Required

If you want unprivileged users to use SMF services, you should create a role sge_admin. Assign this role to the users who should be able to manipulate the Grid Engine SMF services as described here.

Then, you can simply answer y when prompted to use SMF during the installation.

How Do SMF Services Compare to the Normal Services?

The biggest difference between SMF and normal services is that SMF does not consider kill -9 to be a correct service shutdown. SMF interprets kill -9 to restart the service.

Within the SMF framework, a service is uniquely identified by its fault resource management identifier (FMRI).

qmaster Daemon

Service name (FMRI) is svc:/application/sge/qmaster:$SGE_CLUSTER_NAME.

¹ - Restart the daemon if RC scripts were installed

shadowd Daemon

Service name (FMRI) is svc:/application/sge/shadowd:$SGE_CLUSTER_NAME.

¹ - Restart the daemon if RC scripts were installed

execd Daemon

Service name (FMRI) is svc:/application/sge/execd:$SGE_CLUSTER_NAME.

¹ - Restart the daemon if RC scripts were installed

Berkeley RPC Server

Service name (FMRI) is svc:/application/sge/bdb:$SGE_CLUSTER_NAME.

¹ - Restart the server if RC scripts were installed

dbwriter Software

Service name (FMRI) is svc:/application/sge/dbwriter:$SGE_CLUSTER_NAME.

¹ - Restart the dbwriter if RC scripts were installed

Additionally you may use new SMF interfaces to interact with services. For more information, see the svcadm(1M) man page. New actions: Action Command Start service temporary svcadm enable -t FMRI Start service permanently (across reboots) svcadm enable FMRI Stop service temporary svcadm disable -t FMRI Stop service permanently (across reboots) svcadm disable FMRI Restart service svcadm reboot FMRI

<< Previous: Installing Sun Grid Engine Software Interactively

Next: Verifying Sun Grid Engine Installation >>