From: Taylan Kammer Date: Fri, 10 Oct 2025 13:50:56 +0000 (+0200) Subject: man/systemd.service: Improve OOMPolicy documentation (#39212) X-Git-Tag: v259-rc1~349 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F33360%2Fhead;p=thirdparty%2Fsystemd.git man/systemd.service: Improve OOMPolicy documentation (#39212) --- diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 68663e9ed81..125acae4d37 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -1271,11 +1271,13 @@ This setting takes one of continue, stop or kill. If set to continue and a process in the unit is killed by the OOM killer, this is logged but the unit continues running. If set to - stop the event is logged but the unit is terminated cleanly by the service - manager. If set to kill and one of the unit's processes is killed by the OOM - killer the kernel is instructed to kill all remaining processes of the unit too, by setting the - memory.oom.group attribute to 1; also see kernel - page Control Group v2. + stop the event is logged and the unit's processes are terminated cleanly by the + service manager. If set to kill and one of the unit's processes is killed by the + OOM killer the kernel is instructed to kill all remaining processes of the unit too, by setting the + memory.oom.group attribute to 1; also see kernel page + Control Group v2. In case of + both stop and kill, the service ultimately ends up in the + oom-kill failed state after which Restart= may apply. Defaults to the setting DefaultOOMPolicy= in