morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-14 00:14:32 +09:00
Code Issues Packages Projects Releases Wiki Activity

doc: indicate Type=oneshot also detects invocation failures

Browse Source 
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>
This commit is contained in:
Christoph Anton Mitterer
2025-10-20 03:30:58 +02:00
committed by Lennart Poettering
parent 3cc3b469cc
commit a983cf253f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
man/systemd.service.xml
View File

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