Watch
0
0
Fork
You've already forked hyperhive
0

bash OOM order: the stale +1000/task (0) comments say 900 and 1000

This commit is contained in:
maia 2026-11-19 05:15:36 +01:00 • committed by mara
commit ca734f8ea0
2 changed files with 5 additions and 5 deletions

View file

@ -561,8 +561,8 @@ in
# A LOWER OOMScoreAdjust means LESS likely to be killed, so this
# negative value puts the harness — and the agent's own `claude`,
# which it spawns as a child and which therefore inherits the
# value — last in line under memory pressure, behind each subagent
# run (+1000) and bash task (0) (see ./mcp.nix). Losing a
# value — last in line under memory pressure, behind each bash task
# (+1000) and subagent run (+900) (see ./mcp.nix). Losing a
# subagent costs one restartable task; losing this costs the
# session that was supervising it. Not `-1000`, which would
# exempt the harness entirely and leave the kernel with nothing

View file

@ -425,8 +425,8 @@ in
Restart = "always";
RestartSec = 3;
# The daemon runs each subagent run in its own `runs/<name>-<n>/`
# cgroup with `memory.oom.group=1` and `oom_score_adj` +1000, so an
# OOM kill takes one whole run, ahead of a bash task (0) and
# cgroup with `memory.oom.group=1` and `oom_score_adj` +900, so an
# OOM kill takes one whole run, after a bash task (+1000) and ahead of
# `hive-agent` (-500). No `OOMScoreAdjust=` here: the daemon stays
# at 0, and a unit value would also be the floor no run could go
# below. The subgroup name is `DAEMON_SUBGROUP` in hive-agent-sock's