mirror of
https://github.com/mvschwarz/openrig-studio.git
synced 2026-11-07 05:56:21 -10:00
mvschwarz
02d7c9e470
orch named the shape in one line: silence from that check meant BOTH "verified" and "could not ask", so the two outcomes were indistinguishable — a check that cannot fail, which is the same defect class as the one it was added to catch. The query lives behind `if systemctl ... 2>/dev/null; then`, so a failed query skipped the whole block and printed nothing. On a host with no user manager — a container, or systemctl-present-but-unreachable, both already handled elsewhere in this script — the run would look exactly like a verified one. Three outcomes, three distinct lines, none of them silence: systemd agrees; systemd disagrees (a reboot would start the wrong studio); or the query failed and persistence is NOT VERIFIED, with the reason quoted. The last one says explicitly that the unit FILE was checked and what remains unconfirmed is whether the manager picked it up — a daemon-reload that did not take looks identical to success from every runtime check. Driven against four fake systemctl behaviours including the worst one: a non-zero exit with NO message on stderr, which now reports "non-zero, no message" rather than falling through quietly. I had asked cloud-impl to watch this line on a real box to settle whether it degrades quietly. Removing the ambiguity is better than asking someone to observe it — the observation would still have to distinguish two silences.