shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-25 18:50:18 +03:00
Code

man: clarify ManagedOOMPreference documentation

Browse Source 
Explicitly state that ManagedOOMPreference is always honored when the
unit's cgroup is owned by root.
This commit is contained in:
Nick Rosbrook 2022-11-29 15:40:22 -05:00
parent 66bc4f6fb1
commit 3b44e33ff4
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man/systemd.resource-control.xml
View File

@ -1101,10 +1101,10 @@ DeviceAllow=/dev/loop-control
only respect these extended attributes if the unit's cgroup is owned by root.</para>
<para>When calculating candidates to relieve memory pressure, <command>systemd-oomd</command>
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 <command>systemd-oomd</command>
is calculating candidates for <filename>-.slice</filename>, then extended attributes set
on descendants of <filename>/user.slice/user-1000.slice/user@1000.service/</filename>
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 <command>systemd-oomd</command> is calculating candidates for <filename>-.slice</filename>,
then extended attributes set on descendants of <filename>/user.slice/user-1000.slice/user@1000.service/</filename>
will be ignored because the descendants are owned by UID 1000, and <filename>-.slice</filename>
is owned by UID 0. But, if calculating candidates for
<filename>/user.slice/user-1000.slice/user@1000.service/</filename>, then extended attributes set