182 SMF_EXIT_OK 0 Method exited,
183 performing its
184 operation
185 successfully.
186 SMF_EXIT_ERR_FATAL 95 Method failed
187 fatally and is
188 unrecoverable
189 without
190 administrative
191 intervention.
192 SMF_EXIT_ERR_CONFIG 96 Unrecoverable
193 configuration
194 error. A common
195 condition that
196 returns this exit
197 status is the
198 absence of required
199 configuration files
200 for an enabled
201 service instance.
202 SMF_EXIT_ERR_NOSMF 99 Method has been
203 mistakenly invoked
204 outside the smf(5)
205 facility. Services
206 that depend on
207 smf(5) capabilities
208 should exit with
209 this status value.
210 SMF_EXIT_ERR_PERM 100 Method requires a
211 form of permission
212 such as file
213 access, privilege,
214 authorization, or
215 other credential
216 that is not
217 available when
218 invoked.
219 SMF_EXIT_ERR_OTHER non-zero Any non-zero exit
220 status from a
221 method is treated
429 Definitions of exit status codes.
430
431
432 SEE ALSO
433 zonename(1), coreadm(1M), inetd(1M), svccfg(1M), svc.startd(1M),
434 exec(2), fork(2), getdefaultproj(3PROJECT), exec_attr(4), project(4),
435 service_bundle(4), attributes(5), privileges(5), rbac(5), smf(5),
436 smf_bootstrap(5), zones(5), security-flags(5)
437
438 NOTES
439 The present version of smf(5) does not support multiple repositories.
440
441
442 When a service is configured to be started as root but with privileges
443 different from limit_privileges, the resulting process is privilege
444 aware. This can be surprising to developers who expect seteuid(<non-
445 zero UID>) to reduce privileges to basic or less.
446
447
448
449 June 6, 2016 SMF_METHOD(5)
|
182 SMF_EXIT_OK 0 Method exited,
183 performing its
184 operation
185 successfully.
186 SMF_EXIT_ERR_FATAL 95 Method failed
187 fatally and is
188 unrecoverable
189 without
190 administrative
191 intervention.
192 SMF_EXIT_ERR_CONFIG 96 Unrecoverable
193 configuration
194 error. A common
195 condition that
196 returns this exit
197 status is the
198 absence of required
199 configuration files
200 for an enabled
201 service instance.
202 SMF_EXIT_MON_DEGRADE 97 Method encountered
203 some problems and
204 may not be fully
205 functional.
206 SMF_EXIT_ERR_NOSMF 99 Method has been
207 mistakenly invoked
208 outside the smf(5)
209 facility. Services
210 that depend on
211 smf(5) capabilities
212 should exit with
213 this status value.
214 SMF_EXIT_ERR_PERM 100 Method requires a
215 form of permission
216 such as file
217 access, privilege,
218 authorization, or
219 other credential
220 that is not
221 available when
222 invoked.
223 SMF_EXIT_ERR_OTHER non-zero Any non-zero exit
224 status from a
225 method is treated
433 Definitions of exit status codes.
434
435
436 SEE ALSO
437 zonename(1), coreadm(1M), inetd(1M), svccfg(1M), svc.startd(1M),
438 exec(2), fork(2), getdefaultproj(3PROJECT), exec_attr(4), project(4),
439 service_bundle(4), attributes(5), privileges(5), rbac(5), smf(5),
440 smf_bootstrap(5), zones(5), security-flags(5)
441
442 NOTES
443 The present version of smf(5) does not support multiple repositories.
444
445
446 When a service is configured to be started as root but with privileges
447 different from limit_privileges, the resulting process is privilege
448 aware. This can be surprising to developers who expect seteuid(<non-
449 zero UID>) to reduce privileges to basic or less.
450
451
452
453 December 4, 2017 SMF_METHOD(5)
|