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 0b1613a3d15995806931e82983311d8b91a73e1b..40b03d53afa7415535f687ad3693f4f9e0065607 100644 (file)
--- 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 4cf544ad2fcdacb20ece69e4c82bc4eb936f4988..23a7255b88d953724970e27f5f3e1602c0ae931c 100644 (file)
--- 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