]> git.ipfire.org Git - thirdparty/knot-resolver.git/commitdiff
systemd: tweak OOM behavior docs-oom-better-bzu81u/deployments/7244 oom-better 1724/head
authorVladimír Čunát <vladimir.cunat@nic.cz>
Fri, 18 Jul 2025 11:01:06 +0000 (13:01 +0200)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Fri, 18 Jul 2025 11:03:26 +0000 (13:03 +0200)
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

index 4cf544ad2fcdacb20ece69e4c82bc4eb936f4988..23a7255b88d953724970e27f5f3e1602c0ae931c 100644 (file)
@@ -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