From: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Date: Mon, 20 Oct 2025 01:30:58 +0000 (+0200)
Subject: doc: indicate Type=oneshot also detects invocation failures
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a983cf253fd099877eae1fa125c95bdef578a15b;p=thirdparty%2Fsystemd.git

doc: indicate Type=oneshot also detects invocation failures

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 <mail@christoph.anton.mitterer.name>
---

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.</para></listitem>
 
-            <listitem><para>Behavior of <option>oneshot</option> is similar to <option>simple</option>;
+            <listitem><para>Behavior of <option>oneshot</option> is similar to <option>exec</option>;
             however, the service manager will consider the unit up after the main process exits. It will then
             start follow-up units. <varname>RemainAfterExit=</varname> is particularly useful for this type
             of service. <varname>Type=</varname><option>oneshot</option> is the implied default if neither