From a983cf253fd099877eae1fa125c95bdef578a15b Mon Sep 17 00:00:00 2001 From: Christoph Anton Mitterer Date: Mon, 20 Oct 2025 03:30:58 +0200 Subject: [PATCH] doc: indicate Type=oneshot also detects invocation failures MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Type `simple` explicitly mentions that invocation failures like a missing binary or `User=` name won’t get detected – whereas type `exec` mentions that it does. Type `oneshot` refers to being similar to `simple`, which could lead one to assume it doesn’t detect such invocation failures either – it seems however it does. Indicate this my changing its wording to be similar to `exec`. Signed-off-by: Christoph Anton Mitterer --- man/systemd.service.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 84dd17920a1..8c00a093f87 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -206,7 +206,7 @@ identify the main process of the service. The manager will proceed with starting follow-up units after the parent process exits. - Behavior of is similar to ; + Behavior of is similar to ; however, the service manager will consider the unit up after the main process exits. It will then start follow-up units. RemainAfterExit= is particularly useful for this type of service. Type= is the implied default if neither -- 2.47.3