It's an evolution to the now obsolete initialization and termination scripts.
Thus SMF replaces init.d and rc?.d scripts as depicted on init.d(4).
The ? on rc?.d corresponds to the init states as depicted on init(1M).
But SMF is actually more than just an interface for services management:
- It's part of FMA (Fault Management Architecture).
This means it automatically restarts services as possible.
It can notify via SNMP or SMTP on services' state changes.
- It's also a repository of services' properties replacing configuration files.
This is probably the major impact to system administrators.
- Service interdependency documentation.
This means better management and faster troubleshooting.
- Parallel initialization.
This means the system can start way much faster.
After understanding all the advantages of SMF its adoption is quite obvious.
There are excellent how-to articles at Oracle website, such as:
- Introducing the the Basics of SMF
- Advanced Administration with the SMF
- Using svcbundle to Create SMF Manifest and Profiles
- Migrate Control of System Services from Scripts to the SMF
Nevertheless, I'd like to add a few notes and summaries.
I think that my effort can add more help in getting acquainted to SMF.
Here's my SMF post list:
