Read getent's exit code, not its wording (hq issue 213) #88

Merged
mesh-admin merged 1 commits from fix/getent-not-found-is-an-answer into main 2026-10-04 00:11:48 +00:00
1 Commits
Author SHA1 Message Date
jochen 8280a82ef8 Read getent's exit code, not its wording (novox/hq issue 213)
A user that does not exist yet was matched as Go's 'exit status 2', while the host's runner says
'getent exited 2', so it read as a user database that did not answer: the controller's account was
never created and the handover to its process stopped there. The runner keeps the exit underneath
its words, and a caller asks the code.
2026-10-04 02:11:43 +02:00