171
172
173 Exceptional Operations
174 The following subcommands are used for service development and
175 temporary administrative manipulation.
176
177 mark [-It] instance_state {FMRI | pattern}...
178
179 If instance_state is "maintenance", then for each service specified
180 by the operands, svcadm requests that the assigned restarter place
181 the service in the maintenance state. See svc.startd(1M) and
182 inetd(1M) for a detailed description of the actions taken for each
183 restarter.
184
185 If instance_state is "degraded", then for services specified by the
186 operands in the online state, svcadm requests that the restarters
187 assigned to the services move them into the degraded state.
188
189 If the -I option is specified, the request is flagged as immediate.
190
191 The -t option is only valid for maintenance requests. When this
192 option is specified, the request is flagged as temporary, and its
193 effect will only last until the next reboot.
194
195
196 milestone [-d] milestone_FMRI
197
198 If milestone_FMRI is the keyword "none", all services other than
199 the master restarter, svc:/system/svc/restarter:default, will be
200 temporarily disabled.
201
202 If milestone_FMRI is the keyword "all", temporary enable and
203 disable requests for all services will be nullified.
204
205 If milestone_FMRI is one of the following:
206
207 svc:/milestone/single-user:default
208 svc:/milestone/multi-user:default
209 svc:/milestone/multi-user-server:default
210
211
212 then temporary enable and disable requests for the indicated
213 service and all services it depends on (directly or indirectly)
395 libscf(3LIB), contract(4), attributes(5), smf(5), smf_security(5),
396 zones(5)
397
398 NOTES
399 The amount of time svcadm will spend waiting for services and their
400 dependencies to change state is implicitly limited by their method
401 timeouts. For example, a service using the default restarter whose
402 start method hangs will be transitioned to the maintenance state when
403 its timeout expires. svcadm will then consider it impossible for this
404 service to come online without administrator intervention.
405
406
407 Attempts to synchronously enable a service which depends (directly or
408 indirectly) on a file may fail with an exit status indicating that
409 dependencies are unsatisfied if the caller does not have the privileges
410 necessary to search the directory containing the file. This limitation
411 may be removed in a future release.
412
413
414
415 October 17, 2017 SVCADM(1M)
|
171
172
173 Exceptional Operations
174 The following subcommands are used for service development and
175 temporary administrative manipulation.
176
177 mark [-It] instance_state {FMRI | pattern}...
178
179 If instance_state is "maintenance", then for each service specified
180 by the operands, svcadm requests that the assigned restarter place
181 the service in the maintenance state. See svc.startd(1M) and
182 inetd(1M) for a detailed description of the actions taken for each
183 restarter.
184
185 If instance_state is "degraded", then for services specified by the
186 operands in the online state, svcadm requests that the restarters
187 assigned to the services move them into the degraded state.
188
189 If the -I option is specified, the request is flagged as immediate.
190
191 The -t option is mandatory for degrade requests. When this option
192 is specified, the request is flagged as temporary, and its effect
193 will only last until the next reboot.
194
195
196 milestone [-d] milestone_FMRI
197
198 If milestone_FMRI is the keyword "none", all services other than
199 the master restarter, svc:/system/svc/restarter:default, will be
200 temporarily disabled.
201
202 If milestone_FMRI is the keyword "all", temporary enable and
203 disable requests for all services will be nullified.
204
205 If milestone_FMRI is one of the following:
206
207 svc:/milestone/single-user:default
208 svc:/milestone/multi-user:default
209 svc:/milestone/multi-user-server:default
210
211
212 then temporary enable and disable requests for the indicated
213 service and all services it depends on (directly or indirectly)
395 libscf(3LIB), contract(4), attributes(5), smf(5), smf_security(5),
396 zones(5)
397
398 NOTES
399 The amount of time svcadm will spend waiting for services and their
400 dependencies to change state is implicitly limited by their method
401 timeouts. For example, a service using the default restarter whose
402 start method hangs will be transitioned to the maintenance state when
403 its timeout expires. svcadm will then consider it impossible for this
404 service to come online without administrator intervention.
405
406
407 Attempts to synchronously enable a service which depends (directly or
408 indirectly) on a file may fail with an exit status indicating that
409 dependencies are unsatisfied if the caller does not have the privileges
410 necessary to search the directory containing the file. This limitation
411 may be removed in a future release.
412
413
414
415 December 4, 2017 SVCADM(1M)
|