Versions Compared

Old Version 3

changes.mady.by.user Vitaly Shaburov

Saved on

compared with

New Version Current

changes.mady.by.user Vitaly Shaburov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

Layer

Content

admin

Any changes that are made by using the SMF commands or library interfaces, by an administrator or by an application. The admin layer also includes any changes that are made by importing a manifest or applying a profile from a non-standard location. See Importing and Applying Manifests and https://dilos-dev.atlassian.net/wiki/spaces/DS/pages/3286925360/Service+Configuration+Repository#Importing-and-Applying-Manifests-and-Profiles for caution about the use of non-standard locations.

site-profile

Any values from profile files in the /etc/svc/profile/site directory or the legacy /etc/svc/profile/site.xml and /var/svc/profile/site.xml profiles. Note that /var/svc/profile is deprecated as a standard location and should not be used for new profiles.

system-profile

Any values from the /etc/svc/profile/generic.xml and /etc/svc/profile/platform.xml system profiles.

manifest

Values from manifests in the /lib/svc/manifest and /var/svc/manifest directories. Note that /var/svc/manifest is deprecated as a standard location and should not be used for new manifests.

...

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.