From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Tue, 26 Apr 2022 20:05:41 +0000 (+0200)
Subject: man: direct users to systemd-oomd if they read about OOMPolicy
X-Git-Tag: v251-rc2~52^2~1
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3b18f3017c212c3e2a89e18c81bd75c8df3852d8;p=thirdparty%2Fsystemd.git

man: direct users to systemd-oomd if they read about OOMPolicy

OOMPolicy remains valid, but let's push users for the userspace solution.
---

diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index ad303d440b3..fbb77d5e583 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