svcadm(1M)을 검색하려면 섹션에서 1M 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
service_bundle(5)
service_bundle(5) File Formats service_bundle(5)
NAME
service_bundle - service manifest file format
SYNOPSIS
/usr/share/lib/xml/dtd/service_bundle.dtd.1
DESCRIPTION
The service management facility, described in smf(7), utilizes an XML-
based file format to marshal the description of a set of services or
service instances between systems. This file is known as a service bun‐
dle. The primary form of a service bundle is the inventory of services
that are provided by a package, which is called a service manifest.
The DTD describing the service_bundle is provided at
/usr/share/lib/xml/dtd/service_bundle.dtd.1. The attributes and tags
are fully described in the commented DTD. The services supplied with
the operating system, stored under /lib/svc/manifest, provide examples
of correctly formed service descriptions. Manifest and profile file
names can only contain ASCII characters.
service_bundle documents can also use the XML Inclusions (XInclude)
facility to merge multiple documents into one. A service_bundle docu‐
ment manipulator must therefore support the functionality defined by
the XInclude specification.
A complete service description consists of the following:
o A set of properties that identify the service and identify
its restarter
o A set of properties that identify each instance
o A set of framework property groups that describe the frame‐
work's understanding of each instance
o A set of method property groups as required by
svc.startd(8), or by a delegated restarter
o Additional optional method property groups
o A set of dependency property groups
o An optional group of properties that indicate services to
which dependencies on the described service were added
o A set of application property groups or application-specific
typed property groups containing application configuration
data
o A template that describes supporting information about this
service, such as a description, links to documentation, and
metadata about property groups and properties.
The document type definition for the service bundle provides markup to
define each of these aspects of a service description, as well as a
number of entities that identify regular features in describing a ser‐
vice, such as the <create_default_instance> tag.
Manifest Handling During Packaging Operations
Service manifests within packages should be identified with the class
manifestin SVR4 packages and with the attribute restart_fmri=svc:/sys‐
tem/manifest-import:default in IPS packages. Class action scripts that
install and remove service manifests are included in the SVR4 packaging
subsystem. When such a package is installed, the service manifest is
imported.
When a package is uninstalled, service instances in the manifest that
are disabled are deleted. Any services in the manifest with no remain‐
ing instances are also deleted.
If the -R option is supplied to pkg(1), pkgadd(8), or pkgrm(8), the
actions described in this section are done when the system is next
rebooted with that alternate root path.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Availabilitysystem/core-os _ StabilityCommitted
SEE ALSO
libscf(3LIB), attributes(7), locale(7), smf(7), smf_method(7), smf_tem‐
plate(7), pkgadd(8), pkgrm(8), svc.startd(8), svcadm(8), svccfg(8)pkg(1), pkg(7)
NOTES
Nested service_bundle elements must be of the same type.
Oracle Solaris 11.4 26 Mar 2020 service_bundle(5)