stado host beacon-units
Invocation
stado host beacon-unitsPurpose
The unit ids the registry declares for THIS host, one per line. What the health beacon must ask about. The collector's list was an operator-typed `WC_HEALTH_UNITS`, so a service the registry declared and the beacon never watched read as a unit that does not exist: `registry doctor` reported `missing-plist` for `com.wisent.compute.service.stado-resolver.service.service` on ubuntu-server-rtx-pro-6000 while that unit was active with a live pid. Prints nothing and succeeds when this machine is not in the registry or the registry cannot be read: a beacon that fails to collect reports nothing at all, which is worse than reporting the operator's own list.
Required inputs and options
This command has no command-specific inputs or options.
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.