...
Persistent configuration information is stored in layers according to the source of the data. See Repository Layers.
Runtime data, or non-persistent configuration information, is not preserved across reboot, and the repository does not store layer information for non-persistent data. Non-persistent data generally hold an active program state.
...
The service configuration repository can only be manipulated or queried by using SMF interfaces. Use the svcs, svcprop, svcadm, and svccfg commands or the Service Configuration Facility library functions listed in the libscf (3LIB) man page. You can read and write property values and show property values in specified layers and snapshots. For information about layers, see Repository Layers. For information about snapshots, see Repository Snapshots. You can show only the properties of the selected service instance or parent service, or you can show a composed view of properties. In a composed view, both properties set on the parent service and properties set on the service instance are shown; values shown are the values set on the service instance.
...
Local customizations can be provided in profile files with an .xml suffix in the /etc/svc/profile/site directory. If the same property in the same repository layer for the same service or instance is defined by multiple manifests or profiles, SMF cannot determine which value to use. When this type of conflict is detected, the instance is placed in the maintenance state. See Repository Layers for more information about layers.
...
Layer | Content |
| Any changes that are made by using the SMF commands or library interfaces, by an administrator or by an application. The |
| Any values from profile files in the |
| Any values from the |
| Values from manifests in the |
...
You can restore the repository from one of these backups. See How to Restore a Repository From Backup.
Importing and Applying Manifests and Profiles
When you restart the manifest-import service, manifests in standard locations are imported and profiles in standard locations are applied if they are new or changed. See Service Bundles for manifest and profile standard locations. If importing a manifest or applying a profile results in the service being started or stopped, the appropriate method is executed if one exists.
Specifying a file in a standard location to the svccfg import command restarts the manifest-import service.
Recommended best practice is to put your manifest and profile files in the standard locations and restart the manifest-import service rather than use the svccfg import or svccfg apply commands.
| Code Block |
|---|
$ svcadm restart manifest-import |
When you restart the manifest-import service, the configuration in profiles and manifests in standard locations is applied to the manifest, system-profile, or site-profile layer of affected instances, affected instances are refreshed and validated, and a new snapshot is created.