docs(#2754): drop the stale zero-sentinel wording from write_resource_limits

This commit is contained in:
atlas 2026-07-27 10:59:11 +02:00
commit 35d9d79912

View file

@ -536,9 +536,9 @@ fn chmod_socket_dir(agent_name: &str, mode: u32) -> Result<(String, String)> {
/// Two different kinds of setting land in the same file. `MemoryMax=` /
/// `CPUQuota=` are hard caps that throttle even on an idle host;
/// `CPUWeight=` / `IOWeight=` are cgroup v2 relative shares that only
/// decide who yields *under contention*. A zero weight means "not
/// configured" (`None`) and omits the line, so a hive-c0re built before the
/// weights existed keeps producing the old two-line drop-in.
/// decide who yields *under contention*. A weight of `None` means "not
/// configured" and omits the line, so a hive-c0re built before the weights
/// existed keeps producing the old two-line drop-in.
///
/// The condition causes systemd to *skip* (not *fail*) the unit when the
/// bind-mount source dir is absent — result is `condition`, which does not