The service manifest generated with the svcbundle command might meet your needs with no modification necessary. The following example shows a modification of the service manifest.
If you modify a service manifest, use the svccfg validate command to ensure the manifest is still valid.
Example 13-4 Customized Service Manifest : Increase the Time Allowed for the Script to RunIn the following copy of the generated service manifest, the default exec_method timeout of 60 seconds has been increased for the start method. Make sure the start method has adequate time to run the first-boot script.
<?xml version="1.0" ?> <!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'> <!-- Manifest created by svcbundle (2014-Jan-14 16:39:30-0700) --> <service_bundle type="manifest" name="site/first-boot-script-svc"> <service version="1" type="service" name="site/first-boot-script-svc"> <!-- The following dependency keeps us from starting until the multi-user milestone is reached. --> <dependency restart_on="none" type="service" name="multi_user_dependency" grouping="require_all"> <service_fmri value="svc:/milestone/multi-user"/> </dependency> <!-- Make sure the start method has adequate time to run the script. --> <exec_method timeout_seconds="360" type="method" name="start" exec="/opt/site/first-boot-script.sh"/> <!-- The exec attribute below can be changed to a command that SMF should execute to stop the service. See smf_method(5) for more details. --> <exec_method timeout_seconds="60" type="method" name="stop" exec=":true"/> <!-- The exec attribute below can be changed to a command that SMF should execute when the service is refreshed. Services are typically refreshed when their properties are changed in the SMF repository. See smf_method(5) for more details. It is common to retain the value of :true which means that SMF will take no action when the service is refreshed. Alternatively, you may wish to provide a method to reread the SMF repository and act on any configuration changes. --> <exec_method timeout_seconds="60" type="method" name="refresh" exec=":true"/> <property_group type="framework" name="startd"> <propval type="astring" name="duration" value="transient"/> </property_group> <instance enabled="true" name="default"> <property_group type="application" name="config"> <propval type="boolean" name="completed" value="false"/> </property_group> </instance> <template> <common_name> <loctext xml:lang="C"> <!-- Replace this comment with a short name for the service. --> </loctext> </common_name> <description> <loctext xml:lang="C"> <!-- Replace this comment with a brief description of the service --> </loctext> </description> </template> </service> </service_bundle>
$ svccfg validate first-boot-script-svc-manifest.xmlExample 13-5 Customized Service Manifest: Ensure the Script Runs After Non-Global Zones Are Installed
In the following service manifest excerpt, the dependency on svc:/milestone/multi-user is changed to a dependency on svc:/system/zones-install to ensure that the first-boot script runs after all non-global zones are installed.
<!-- The following dependency keeps us from starting until all non-global zones are installed. --> <dependency restart_on="none" type="service" name="ngz_dependency" grouping="require_all"> <service_fmri value="svc:/system/zones-install"/> </dependency>