Specifications

Red Hat Enterprise Linux to Oracle Solaris Porting Guide
82
You can disable a service with the following command, where service name is the name of the
service that you want to disable:
#svcadm disable service name
Managing Service Dependencies in Oracle Solaris
SMF provides a simple mechanism for defining the relationships among various services so that
dependent services can be automatically restarted when necessary. Information necessary to manage
each service is stored in the service repository. This information allows the restarter to move the
service from one state to another state. Each service is managed by a service restarter, which carries
out the administrative actions.
The service configuration repository provides a per-service snapshot at the time each service is
successfully started so that fallback is possible. This capability helps you debug service configuration
problems easily.
The fundamental unit of administration in the SMF framework is the service instance. Each SMF
service has the potential to have multiple versions of it configured, as well multiple instances of the
same version running on a single system.
An instance is a specific configuration of a service, for example, a Web server is a service and a specific
Web server daemon that is configured to listen on port 8080 is an instance. Each instance of the Web
server service can be configured to have different specifications. The Web service will have
system-wide configuration settings, and each instance can choose to override specific configuration.
Migrating to SMF
Migrating services from RHEL to Oracle Solaris SMF is not a difficult task because SMF preserves
compatibility with legacy services. Legacy refers to /etc/rc*.d, /etc/init.d, and
/etc/inittab scripts, which are popularly used in RHEL environments. Legacy services can
continue to work as they did previously, but you will be able to observe these services with SMF.
However, to exploit all the advantages of SMF, such as self-healing capabilities or service restart, you
need to convert the scripts to SMF manifests.
Service Manifests
Information regarding services, service properties, property groups, and instances is added to the SMF
repository. This information is stored in a service manifest that SMF uses when managing services as well
as when determining the root causes of service failures. The service manifest also describes the
conditions under which failed services may be automatically restarted. A separate service manifest is
required per service/application. Oracle Solaris provides some service manifests by default. Optionally,
you can customize these manifests or write your own for other services.