diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-04-29 14:27:23 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-04-29 14:27:23 -0400 |
| commit | 26ccc1d0875b0e0c4306b03a52aff712c23d46c7 (patch) | |
| tree | 4907223eceff5cfdd2556a5305f9a3c01801435f /man | |
| parent | 1c5ed0e2b4923b12be52c9c3e8f43682403dcf32 (diff) | |
| parent | 94a0ef6e572896140b8f28f688e881e198e2f2ab (diff) | |
Merge pull request #3151 from keszybz/pr3149-2
Assorted fixes #3149 + one commit tacked on top
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemd.timer.xml | 6 |
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> |