JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Managing Services and Faults in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  Managing Services (Overview)

About SMF in this Release

Introduction to SMF

Advantages to Using SMF

SMF Concepts

SMF Service

SMF Dependencies

Service Identifiers

Service States

SMF Manifests

SMF Profiles

Service Configuration Repository

SMF Administrative Layers

SMF Repository Backups

SMF Snapshots

SMF Service Error Logging

SMF Administrative and Programming Interfaces

SMF Command-Line Administrative Utilities

Service Management Configuration Library Interfaces

SMF Components

SMF Master Restarter Daemon

SMF Delegated Restarters

SMF Properties and Property Groups

Managing Information in the Service Configuration Repository

Viewing SMF Information

Modifying SMF Information

Deleting SMF Information

SMF and Booting

SMF Compatibility

Run Levels

When to Use Run Levels or Milestones

Determining a System's Run Level

/etc/inittab File

What Happens When the System Is Brought to Run Level 3

2.  Managing Services (Tasks)

3.  Using the Fault Manager


Introduction to SMF

SMF makes it easier to manage applications and system services. The framework infrastructure augments the traditional UNIX startup scripts, init run levels, and configuration files. SMF provides a mechanism to define the relationships between applications or services, so that dependent services can automatically be restarted when necessary. Information needed to manage each service is stored in the service configuration repository, which provides a simplified way to manage each service.

SMF defines a set of actions that can be invoked on a service by an administrator. These actions, which can be manually manipulated by the svcadm command, include enable, disable, refresh, restart, and mark. Each service is managed by a service restarter, which carries out the administrative actions. In general, the restarters carry out actions by executing methods for a service. Methods for each service are defined in the service configuration repository. These methods allow the restarter to move the service from one state to another state.

The service configuration repository provides a per-service snapshot at the time that each service is successfully started so that fallback is possible. In addition, the repository provides a consistent and persistent way to enable or disable a service, as well as a consistent view of service states. This capability helps you debug service configuration problems.