166 that are required by the restarter but which are unnecessary for
167 the particular service implementation.
168
169
170 Exiting and Exit Status
171 The required behavior of a start method is to delay exiting until the
172 service instance is ready to answer requests or is otherwise
173 functional.
174
175
176 The following exit status codes are defined in <libscf.h> and in the
177 shell support file.
178
179
180
181
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
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)
|
166 that are required by the restarter but which are unnecessary for
167 the particular service implementation.
168
169
170 Exiting and Exit Status
171 The required behavior of a start method is to delay exiting until the
172 service instance is ready to answer requests or is otherwise
173 functional.
174
175
176 The following exit status codes are defined in <libscf.h> and in the
177 shell support file.
178
179
180
181
182 SMF_EXIT_OK 0 Method exited,
183 performing its
184 operation
185 successfully.
186 SMF_EXIT_NODAEMON 94 Method exited
187 successfully but
188 purposefully leaves
189 no processes
190 remaining in the
191 contract; it should
192 be treated as if it
193 had a transient
194 service model.
195 SMF_EXIT_ERR_FATAL 95 Method failed
196 fatally and is
197 unrecoverable
198 without
199 administrative
200 intervention.
201 SMF_EXIT_ERR_CONFIG 96 Unrecoverable
202 configuration
203 error. A common
204 condition that
205 returns this exit
206 status is the
207 absence of required
208 configuration files
209 for an enabled
210 service instance.
211 SMF_EXIT_ERR_NOSMF 99 Method has been
212 mistakenly invoked
213 outside the smf(5)
214 facility. Services
438 Definitions of exit status codes.
439
440
441 SEE ALSO
442 zonename(1), coreadm(1M), inetd(1M), svccfg(1M), svc.startd(1M),
443 exec(2), fork(2), getdefaultproj(3PROJECT), exec_attr(4), project(4),
444 service_bundle(4), attributes(5), privileges(5), rbac(5), smf(5),
445 smf_bootstrap(5), zones(5), security-flags(5)
446
447 NOTES
448 The present version of smf(5) does not support multiple repositories.
449
450
451 When a service is configured to be started as root but with privileges
452 different from limit_privileges, the resulting process is privilege
453 aware. This can be surprising to developers who expect seteuid(<non-
454 zero UID>) to reduce privileges to basic or less.
455
456
457
458 February 25, 2019 SMF_METHOD(5)
|