pub const HERMIT_DEADLINE_EXIT: i32 = 124;Expand description
A deadline hermit itself was asked to enforce expired: 124.
The status the container init exits with when a hermit-owned bound ends the
run – run --timeout’s SIGALRM fallback here, and record --record-timeout’s
handler in record_start.rs, which has always used this value. 124 is the
established code for “a deadline fired” across GNU timeout, safehermit’s
wall bound and both hermit spellings, so this names an existing convention
rather than claiming a new number.
⚠️ IT MUST BE READ AT THE CONTAINER BOUNDARY OR IT IS SILENTLY REWRITTEN TO
125. Found only by forcing the fallback to fire, 2026-08-26: the init exited
124, classify_container_result had no arm for it, and it fell through to
ContainerChildExit – so the run reported exit 125 and
class=container-child-exit, “the child died with a status it did not
pick”, for a deadline hermit chose to enforce. Identical in shape to the
refusal that arrives as 122 and needs its own arm for the same reason.