shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-23 21:35:11 +03:00
Code

man: Mention Type=oneshot timeout directive

Browse Source 
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.
This commit is contained in:
Lucas Werkmeister 2024-07-16 18:15:32 +02:00 committed by Daan De Meyer
parent 20de757b69
commit 8c4aa0f1c6
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
man/systemd.service.xml
View File

@ -727,8 +727,8 @@
<listitem><para>Configures a maximum time for the service to run. If this is used and the service has been
active for longer than the specified time it is terminated and put into a failure state. Note that this setting
does not have any effect on <varname>Type=oneshot</varname> services, as they terminate immediately after
activation completed. Pass <literal>infinity</literal> (the default) to configure no runtime
limit.</para>
activation completed (use <varname>TimeoutStartSec=</varname> to limit their activation).
Pass <literal>infinity</literal> (the default) to configure no runtime limit.</para>
<para>If a service of <varname>Type=notify</varname>/<varname>Type=notify-reload</varname> sends
<literal>EXTEND_TIMEOUT_USEC=…</literal>, this may cause the runtime to be extended beyond