An astring (as defined in scf_value_is_type; see scf_value_is_type(3SCF)) that describes the default level of messages to print to the console during boot. The supported message options include quiet and verbose. The quiet option prints minimal messages to console during boot. The verbose option prints a single message per service started to indicate success or failure. You can use the boot -m option to override the boot_messages setting at boot time. See kernel(8).

Control the level of global service logging for svc.startd. An astring (as defined in scf_value_is_type; see scf_value_is_type(3SCF)) that describes the default level of messages to log to syslog (see syslog(3C) and svc.startd's global logfile, /var/svc/log/svc.startd.log. The supported message options include quiet, verbose, and debug. The quiet option sends error messages requiring administrative intervention to the console, syslog and svc.startd's global logfile. The verbose option sends error messages requiring administrative intervention to the console, syslog and svc.startd's global logfile, and information about errors which do not require administrative intervention to svc.startd's global logfile. A single message per service started is also sent to the console. The debug option sends svc.startd debug messages to svc.startd's global logfile, error messages requiring administrative intervention to the console, syslog and svc.startd's global logfile, and a single message per service started to the console.

An FMRI which determines the milestone used as the default boot level. Acceptable options include only the major milestones:

svc:/milestone/single-user:default
svc:/milestone/multi-user:default
svc:/milestone/multi-user-server:default

Indicates that a reconfiguration reboot has been requested. Services with actions that must key off of a reconfiguration reboot may check that this property exists and is set to 1 to confirm a reconfiguration boot has been requested. This property is managed by svc.startd and should not be modified by the administrator.

The current and next (if currently in transition) state for an instance.

A caption detailing additional information about the current instance state. The auxiliary state available for services managed by svc.startd is: maintenance

fault_threshold_reached
stop_method_failed
administrative_request

The time when the current state was reached.

The primary process contract ID, if any, that under which the service instance is executing.

Reload any appropriate configuration parameters from the repository or config file, without interrupting service. This is often implemented using SIGHUP for system daemons. If the service is unable to recognize configuration changes without a restart, no refresh method is provided. This method is optional.

Start the service. Return success only after the application is available to consumers. Fail if a conflicting instance is already running, or if the service is unable to start. This method is required.

Stop the service. In some cases, the stop method can be invoked when some or all of the service has already been stopped. Only return an error if the service is not entirely stopped on method return. This method is required.

If enabled is set to true, the restarter attempts to start the service once all its dependencies are satisfied. If set to false, the service remains in the disabled state, not running.

If this FMRI property is empty or set to svc:/system/svc/restarter:default, the service is managed by svc.startd. Otherwise, the restarter specified is responsible (once it is available) for managing the service.

This was originally supposed to ensure that only one service instance could be in online or degraded state at once; however, it was never implemented, and is often incorrectly specified in multi-instance manifests. As such, it should be considered obsolete and not specified in new manifests.

The critical_failure_count and critical_failure_period properties together specify the maximum number of service failures allowed in a given time interval before svc.startd transitions the service to maintenance. If the number of failures exceeds critical_failure_count in any period of critical_failure_period seconds, svc.startd will transition the service to maintenance.

The duration property defines the service's model. It can be set to transient, child also known as "wait" model services, or contract (the default).

The ignore_error property, if set, specifies a comma-separated list of ignored events. Legitimate string values in that list are core and signal. The default is to restart on all errors.

The need_session property, if set to true, indicates that the instance should be launched in its own session. The default is not to do so.

The utmpx_prefix string property defines that the instance requires a valid utmpx entry prior to start method execution. The default is not to create a utmpx entry.

all processes in the service exit

any processes in the service produce a core dump

a process outside the service sends a service process a fatal signal (for example, an administrator terminates a service process with the pkill command)

Single-user (S)

Multi-user (2)

Multi-user with network services (3)

Directory where svc.startd stores log files.

Directory where svc.startd stores log files in early stages of boot, before /var is mounted read-write.