386            Definitions of exit status codes.
 387 
 388 
 389 SEE ALSO
 390        zonename(1), coreadm(1M), inetd(1M), svccfg(1M), svc.startd(1M),
 391        exec(2), fork(2), getdefaultproj(3PROJECT), exec_attr(4), project(4),
 392        service_bundle(4), attributes(5), privileges(5), rbac(5), smf(5),
 393        smf_bootstrap(5), zones(5), security-flags(5)
 394 
 395 NOTES
 396        The present version of smf(5) does not support multiple repositories.
 397 
 398 
 399        When a service is configured to be started as root but with privileges
 400        different from limit_privileges, the resulting process is privilege
 401        aware.  This can be surprising to developers who expect seteuid(<non-
 402        zero UID>) to reduce privileges to basic      or less.
 403 
 404 
 405 
 406                                  May 20, 2009                    SMF_METHOD(5)

 386            Definitions of exit status codes.
 387 
 388 
 389 SEE ALSO
 390        zonename(1), coreadm(1M), inetd(1M), svccfg(1M), svc.startd(1M),
 391        exec(2), fork(2), getdefaultproj(3PROJECT), exec_attr(4), project(4),
 392        service_bundle(4), attributes(5), privileges(5), rbac(5), smf(5),
 393        smf_bootstrap(5), zones(5), security-flags(5)
 394 
 395 NOTES
 396        The present version of smf(5) does not support multiple repositories.
 397 
 398 
 399        When a service is configured to be started as root but with privileges
 400        different from limit_privileges, the resulting process is privilege
 401        aware.  This can be surprising to developers who expect seteuid(<non-
 402        zero UID>) to reduce privileges to basic      or less.
 403 
 404 
 405 
 406                                  June 6, 2016                    SMF_METHOD(5)