bash OOM order: the stale +1000/task (0) comments say 900 and 1000
This commit is contained in:
parent
dfe8f9eac0
commit
ca734f8ea0
1 changed files with 5 additions and 5 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in a new issue