From: Vladimír Čunát <vladimir.cunat@nic.cz>
Date: Fri, 18 Jul 2025 11:01:06 +0000 (+0200)
Subject: systemd: tweak OOM behavior
X-Git-Tag: v6.0.16~2^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=51485cdcc467284ea1d8eb6b65eab8d49cccf8ce;p=thirdparty%2Fknot-resolver.git

systemd: tweak OOM behavior

When OOM killer happens, it's basically always killing kresd
process(es), in which case the supervisord inside should simply
restart them and everything should be OK.

I.e. in almost all cases there's no need for systemd to panic
and stop the whole knot-resolver service.
---

diff --git a/NEWS b/NEWS
index 0b1613a3d..40b03d53a 100644
--- a/NEWS
+++ b/NEWS
@@ -7,6 +7,9 @@ Improvements
 - manager: force a configuration reload via management HTTP API 'api/reload/force' (#939, !1748)
   - kresctl: reload: added '--force' flag
 - /fallback: add this feature/module (!1733)
+- systemd: do not force-fail knot-resolver.service on OOM (!1724)
+  In basically all cases the OOM killer will kill a kresd process
+  and supervisord will just restart it, and everything will keep working.
 
 Bugfixes
 --------
diff --git a/systemd/knot-resolver.service.in b/systemd/knot-resolver.service.in
index 4cf544ad2..23a7255b8 100644
--- a/systemd/knot-resolver.service.in
+++ b/systemd/knot-resolver.service.in
@@ -18,6 +18,7 @@ User=@user@
 Group=@group@
 CapabilityBoundingSet=CAP_NET_BIND_SERVICE CAP_SETPCAP
 AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_SETPCAP
+OOMPolicy=continue
 
 [Install]
-WantedBy=multi-user.target
\ No newline at end of file
+WantedBy=multi-user.target