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.
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