243        specific way in which these general properties interacts with
 244        svc.startd follows:
 245 
 246        general/enabled
 247 
 248            If enabled is set to true, the restarter attempts to start the
 249            service once all its dependencies are satisfied. If set to false,
 250            the service remains in the disabled state, not running.
 251 
 252 
 253        general/restarter
 254 
 255            If this FMRI property is empty or set to
 256            svc:/system/svc/restarter:default, the service is managed by
 257            svc.startd. Otherwise, the restarter specified is responsible (once
 258            it is available) for managing the service.
 259 
 260 
 261        general/single_instance
 262 
 263            If single_instance is set to true, svc.startd only allows one
 264            instance of this service to transition to online or degraded at any
 265            time.


 266 
 267 
 268 
 269        Additionally, svc.startd managed services can define the optional
 270        properties listed below in the startd property group.
 271 
 272        startd/critical_failure_count
 273        startd/critical_failure_period
 274 
 275            The critical_failure_count and critical_failure_period properties
 276            together specify the maximum number of service failures allowed in
 277            a given time interval before svc.startd transitions the service to
 278            maintenance.  If the number of failures exceeds
 279            critical_failure_count in any period of critical_failure_period
 280            seconds, svc.startd will transition the service to maintenance.
 281 
 282 
 283        startd/duration
 284 
 285            The duration property defines the service's model. It can be set to

 420          # /usr/sbin/svccfg -s system/svc/restarter:default
 421          svc:/system/svc/restarter:default> addpg options application
 422          svc:/system/svc/restarter:default> setprop options/logging = \
 423          astring: verbose
 424          svc:/system/svc/restarter:default> exit
 425 
 426 
 427 
 428 
 429        This request will take effect on the next restart of svc.startd.
 430 
 431 
 432 SEE ALSO
 433        svcs(1), svcprop(1), kernel(1M), init(1M), svcadm(1M), svccfg(1M),
 434        svc.configd(1M), setsid(2), syslog(3C), libscf(3LIB),
 435        scf_value_is_type(3SCF), contract(4), init.d(4), process(4),
 436        inittab(4), attributes(5), smf(5), smf_method(5)
 437 
 438 
 439 
 440                                 March 18, 2011                  SVC.STARTD(1M)

 243        specific way in which these general properties interacts with
 244        svc.startd follows:
 245 
 246        general/enabled
 247 
 248            If enabled is set to true, the restarter attempts to start the
 249            service once all its dependencies are satisfied. If set to false,
 250            the service remains in the disabled state, not running.
 251 
 252 
 253        general/restarter
 254 
 255            If this FMRI property is empty or set to
 256            svc:/system/svc/restarter:default, the service is managed by
 257            svc.startd. Otherwise, the restarter specified is responsible (once
 258            it is available) for managing the service.
 259 
 260 
 261        general/single_instance
 262 
 263            This was originally supposed to ensure that only one service
 264            instance could be in online or degraded state at once; however, it
 265            was never implemented, and is often incorrectly specified in multi-
 266            instance manifests. As such, it should be considered obsolete and
 267            not specified in new manifests.
 268 
 269 
 270 
 271        Additionally, svc.startd managed services can define the optional
 272        properties listed below in the startd property group.
 273 
 274        startd/critical_failure_count
 275        startd/critical_failure_period
 276 
 277            The critical_failure_count and critical_failure_period properties
 278            together specify the maximum number of service failures allowed in
 279            a given time interval before svc.startd transitions the service to
 280            maintenance.  If the number of failures exceeds
 281            critical_failure_count in any period of critical_failure_period
 282            seconds, svc.startd will transition the service to maintenance.
 283 
 284 
 285        startd/duration
 286 
 287            The duration property defines the service's model. It can be set to

 422          # /usr/sbin/svccfg -s system/svc/restarter:default
 423          svc:/system/svc/restarter:default> addpg options application
 424          svc:/system/svc/restarter:default> setprop options/logging = \
 425          astring: verbose
 426          svc:/system/svc/restarter:default> exit
 427 
 428 
 429 
 430 
 431        This request will take effect on the next restart of svc.startd.
 432 
 433 
 434 SEE ALSO
 435        svcs(1), svcprop(1), kernel(1M), init(1M), svcadm(1M), svccfg(1M),
 436        svc.configd(1M), setsid(2), syslog(3C), libscf(3LIB),
 437        scf_value_is_type(3SCF), contract(4), init.d(4), process(4),
 438        inittab(4), attributes(5), smf(5), smf_method(5)
 439 
 440 
 441 
 442                                December 11, 2019                SVC.STARTD(1M)