Skip to content

Commit 9e3972e

Browse files
lucaswerkmeisterbluca
authored andcommitted
man: Mention Type=oneshot timeout directive
Make the warning for oneshot services (where RuntimeMaxSec= has no effect) more actionable by pointing to the directive people can use instead to effectively limit their runtime. (cherry picked from commit 8c4aa0f) (cherry picked from commit 468b064) (cherry picked from commit 017d7fd) (cherry picked from commit a7e6ebc) (cherry picked from commit 7b09e91)
1 parent e4d44bc commit 9e3972e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

man/systemd.service.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -707,8 +707,8 @@
707707
<listitem><para>Configures a maximum time for the service to run. If this is used and the service has been
708708
active for longer than the specified time it is terminated and put into a failure state. Note that this setting
709709
does not have any effect on <varname>Type=oneshot</varname> services, as they terminate immediately after
710-
activation completed. Pass <literal>infinity</literal> (the default) to configure no runtime
711-
limit.</para>
710+
activation completed (use <varname>TimeoutStartSec=</varname> to limit their activation).
711+
Pass <literal>infinity</literal> (the default) to configure no runtime limit.</para>
712712

713713
<para>If a service of <varname>Type=notify</varname> sends <literal>EXTEND_TIMEOUT_USEC=…</literal>, this may cause
714714
the runtime to be extended beyond <varname>RuntimeMaxSec=</varname>. The first receipt of this message

0 commit comments

Comments
 (0)