diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-04-26 22:05:41 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-04-28 15:46:44 +0200 |
| commit | 3b18f3017c212c3e2a89e18c81bd75c8df3852d8 (patch) | |
| tree | dbdb5e2d118b4b09efd9cd9cb12d7eea334573fb /man/systemd.service.xml | |
| parent | 6f83ea60e90b18e44cc979834aae2947afa66834 (diff) | |
| download | systemd-3b18f3017c212c3e2a89e18c81bd75c8df3852d8.tar.gz | |
man: direct users to systemd-oomd if they read about OOMPolicy
OOMPolicy remains valid, but let's push users for the userspace solution.
Diffstat (limited to 'man/systemd.service.xml')
| -rw-r--r-- | man/systemd.service.xml | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index ad303d440b..fbb77d5e58 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -1123,8 +1123,14 @@ <varlistentry> <term><varname>OOMPolicy=</varname></term> - <listitem><para>Configure the Out-Of-Memory (OOM) killer policy. On Linux, when memory becomes scarce - the kernel might decide to kill a running process in order to free up memory and reduce memory + <listitem><para>Configure the out-of-memory (OOM) kernel killer policy. Note that the userspace OOM + killer + <citerefentry><refentrytitle>systemd-oomd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> + is a more flexible solution that aims to prevent out-of-memory situations for the userspace, not just + the kernel.</para> + + <para>On Linux, when memory becomes scarce to the point that the kernel has trouble allocating memory + for itself, it might decide to kill a running process in order to free up memory and reduce memory pressure. This setting takes one of <constant>continue</constant>, <constant>stop</constant> or <constant>kill</constant>. If set to <constant>continue</constant> and a process of the service is killed by the kernel's OOM killer this is logged but the service continues running. If set to |