From 3b44e33ff4fb2896244ff5b461b29b4ef7c10803 Mon Sep 17 00:00:00 2001 From: Nick Rosbrook Date: Tue, 29 Nov 2022 15:40:22 -0500 Subject: [PATCH] man: clarify ManagedOOMPreference documentation Explicitly state that ManagedOOMPreference is always honored when the unit's cgroup is owned by root. --- man/systemd.resource-control.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index fe875a81c3..1142ad7758 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -1101,10 +1101,10 @@ DeviceAllow=/dev/loop-control only respect these extended attributes if the unit's cgroup is owned by root. When calculating candidates to relieve memory pressure, systemd-oomd - will only respect these extended attributes if the unit's cgroup owner, and the - owner of the monitored ancestor cgroup are the same. For example, if systemd-oomd - is calculating candidates for -.slice, then extended attributes set - on descendants of /user.slice/user-1000.slice/user@1000.service/ + will only respect these extended attributes if the unit's cgroup is owned by root, or if the + unit's cgroup owner, and the owner of the monitored ancestor cgroup are the same. For example, + if systemd-oomd is calculating candidates for -.slice, + then extended attributes set on descendants of /user.slice/user-1000.slice/user@1000.service/ will be ignored because the descendants are owned by UID 1000, and -.slice is owned by UID 0. But, if calculating candidates for /user.slice/user-1000.slice/user@1000.service/, then extended attributes set