pub const HERMIT_LOG_CAP_EXIT: i32 = 123;Expand description
Hermit’s own log output exceeded --max-log-bytes: 123.
The status hermit exits with when the byte budget on its tracing output
(stderr, or --log-file) is exhausted and it deliberately tears the run
down. 123 was already reserved below for “a LOG BYTE CAP fired” on behalf of
dev-hermit’s bin/safehermit; this is the same event enforced one layer
lower, exactly as 124 is shared by hermit’s --timeout and safehermit’s wall
deadline. It is not 125 because the cap working is not hermit breaking, and
not 122 because no fail-closed determinism policy was involved: the remedy
is “lower the log level or raise the cap”, not “change the program”.
Like 124, it must be read at the container boundary
(classify_container_result) or it is rewritten to 125.