fix(wake): close fd 9 in the detector's sleep child so a dead detector's lock dies with it #993

Merged
Mos merged 4 commits from fix/966-detector-lock-fd-leak into main 2026-07-31 13:48:34 +00:00
Showing only changes of commit b648079fad - Show all commits
@@ -531,7 +531,13 @@ cmd_run() {
[ "$once" -eq 1 ] && break
# Close the detector lock fd in the sleep child; otherwise an orphaned sleep
# keeps the single-instance flock (fd 9, taken at exec 9> above) alive after
# the detector parent dies, and no replacement instance can ever acquire it.
# the detector parent dies. The lock is non-blocking (`flock -n`, above), so
# for as long as that sleep survives a replacement instance is REFUSED and
# exits rather than queueing. The window is BOUNDED by one poll interval
# (WAKE_DETECTOR_INTERVAL, default 30s): when the orphaned sleep exits the
# last copy of the fd closes and the next start succeeds. The cost is a
# restart window in which every supervisor retry fails — not a lock that
# nothing can ever reclaim.
# `9>&-` closes ONLY the child's copy — the parent's lock is unaffected.
sleep "$interval" 9>&-
done