stado service unit logs
Invocation
stado service unit logs [OPTIONS] --host <HOST> --lines <LINES> <LABEL>Purpose
The tail of one unit's own log on HOST, named by its label whether or not the registry declares it. A crash-looping unit says why in its log and nowhere else: the health beacon reports it failed and carries no log, and `host exec` is a read-only allowlist that cannot read a file. `service logs` reads a declared service on every host that manages it; this reads one label on one host.
Required inputs and options
| Input or option | Contract |
|---|---|
<LABEL> | Unit label as launchd knows it, e.g. com.wisent.brama |
--host <HOST> | Registry host to read |
--lines <LINES> | Tail this many lines from each declared log path |
--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.