diff options
| author | Lennart Poettering <lennart@poettering.net> | 2023-02-24 10:42:10 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2023-03-01 09:43:24 +0100 |
| commit | 9d03637404a7e53dee2d47b3d5d1dc47b59997e9 (patch) | |
| tree | 369b3e65fc59d3098935b71d3144b7489bd1c6ae /units/user@.service.in | |
| parent | pid1: add unit file settings to control memory pressure logic (diff) | |
| download | systemd-9d03637404a7e53dee2d47b3d5d1dc47b59997e9.tar.xz systemd-9d03637404a7e53dee2d47b3d5d1dc47b59997e9.zip | |
units: let systemd --user manage its own memory pressure handling
Let's make things systematic: the per-user and the per-system manager
should manage their own memory pressure, as they are, well, managers of
things.
This is particularly relevant and the per-user service manager should
watch its own "init.scope" subcgroup, instead of the main service unit
cgroup, and hence $MEMORY_PRESSURE_WATCH as set by the per-system
service manager would simply be wrong.
Diffstat (limited to 'units/user@.service.in')
| -rw-r--r-- | units/user@.service.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/units/user@.service.in b/units/user@.service.in index 5e95efe1d1..0c3440bb3f 100644 --- a/units/user@.service.in +++ b/units/user@.service.in @@ -26,3 +26,4 @@ TasksMax=infinity TimeoutStopSec={{ DEFAULT_USER_TIMEOUT_SEC*4//3 }}s KeyringMode=inherit OOMScoreAdjust=100 +MemoryPressureWatch=skip |