From e9b8aa82aa346a4fdf1d2cd2c374e9cdd0f2a6ce Mon Sep 17 00:00:00 2001 From: =?utf8?q?Vladim=C3=ADr=20=C4=8Cun=C3=A1t?= Date: Fri, 18 Jul 2025 13:01:06 +0200 Subject: [PATCH] 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. --- systemd/knot-resolver.service.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 -- 2.47.2