Skip to content

Commit a7e6ebc

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)
1 parent 32a3200 commit a7e6ebc

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
@@ -711,8 +711,8 @@
711711
<listitem><para>Configures a maximum time for the service to run. If this is used and the service has been
712712
active for longer than the specified time it is terminated and put into a failure state. Note that this setting
713713
does not have any effect on <varname>Type=oneshot</varname> services, as they terminate immediately after
714-
activation completed. Pass <literal>infinity</literal> (the default) to configure no runtime
715-
limit.</para>
714+
activation completed (use <varname>TimeoutStartSec=</varname> to limit their activation).
715+
Pass <literal>infinity</literal> (the default) to configure no runtime limit.</para>
716716

717717
<para>If a service of <varname>Type=notify</varname>/<varname>Type=notify-reload</varname> sends
718718
<literal>EXTEND_TIMEOUT_USEC=…</literal>, this may cause the runtime to be extended beyond

0 commit comments

Comments
 (0)