From: Lennart Poettering <lennart@poettering.net>
Date: Fri, 29 Apr 2016 11:36:38 +0000 (+0200)
Subject: man: document that RemainAfterExit= doesn't make much sense for repetitive timers
X-Git-Tag: v230~108^2~3
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=14e2baa369b120788322e727ecdd249127a13fa1;p=thirdparty%2Fsystemd.git

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

Fixes #3122
---

diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index eb0afee1412..0d0cccf1522 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>