summaryrefslogtreecommitdiff
path: root/man/systemd.timer.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2016-04-29 13:36:38 +0200
committerLennart Poettering <lennart@poettering.net>2016-04-29 13:37:33 +0200
commit14e2baa369b120788322e727ecdd249127a13fa1 (patch)
tree9903ae3618a73bfa5574d62a4b8ce3d23da5d8a0 /man/systemd.timer.xml
parent941060bf5efae24eb9879e42444e15c649973473 (diff)
man: document that RemainAfterExit= doesn't make much sense for repetitive timers
Fixes #3122
Diffstat (limited to 'man/systemd.timer.xml')
-rw-r--r--man/systemd.timer.xml6
1 files changed, 6 insertions, 0 deletions
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index eb0afee141..0d0cccf152 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -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>