From 705cb712aebeb78f744c5f87d37ffa3a88e7ec12 Mon Sep 17 00:00:00 2001 From: Taylan Kammer Date: Fri, 10 Oct 2025 15:50:56 +0200 Subject: [PATCH] man/systemd.service: Improve OOMPolicy documentation (#39212) --- man/systemd.service.xml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) 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 -- 2.47.3