shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-09 01:18:19 +03:00
Code

man: document that RemainAfterExit= doesn't make much sense for repetitive timers

Browse Source 
Fixes #3122
This commit is contained in:
Lennart Poettering 2016-04-29 13:36:38 +02:00
parent 941060bf5e
commit 14e2baa369
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
man/systemd.timer.xml
View File

@ -73,6 +73,12 @@
<filename>foo.timer</filename> activates a matching service
<filename>foo.service</filename>. The unit to activate may be
controlled by <varname>Unit=</varname> (see below).</para>
<para>Note that in case the unit to activate is already active at the time the timer elapses it is not restarted,
but simply left running. There is no concept of spawning new service instances in this case. Due to this, services
with <varname>RemainAfterExit=</varname> set (which stay around continously even after the service's main process
exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and
then stay around forever.</para>
</refsect1>
<refsect1>