stado service bootout
Invocation
stado service bootout [OPTIONS] --host <HOST> <LABEL>Purpose
Boot one exact launchd label or systemd unit out of its system or user scope. `stop` and `retire` require a registry declaration. This command is for a loaded unit the registry does not declare, including an obsolete duplicate that `service list --undeclared` found. It never removes the unit's file. On Linux the selected systemd manager stops and disables only the exact requested unit, then Stado reads back that it is inactive and not enabled. On Darwin the selected launchd domain is booted out as before.
Required inputs and options
| Input or option | Contract |
|---|---|
<LABEL> | Exact launchd label or systemd unit name, as the host knows it |
--host <HOST> | Registry host that has it loaded |
--domain <DOMAIN> | Which init-system scope to act in: `system`, `user`, or unset for `any`. The unset order is system first, then the calling account only when the system scope holds no exact unit by this name. A name loaded in both scopes identifies two jobs; pass `user` to leave its system sibling untouched |
--json | Command option; required or optional as shown in the invocation. |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.