From cc4e4df49fe38e076c74b652f7e01b6c54004cab Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 8 Apr 2016 19:00:00 +0200 Subject: man: clarify that DefaultDependencies= is in the [Unit] section This hopefully reduces confusion resulting in issues like #2992. --- man/systemd.timer.xml | 24 +++++++++--------------- 1 file changed, 9 insertions(+), 15 deletions(-) (limited to 'man/systemd.timer.xml') diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 29e235e2dc..22c83f790f 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -81,21 +81,15 @@ Timer units automatically gain a Before= dependency on the service they are supposed to activate. - Unless DefaultDependencies= is set to - , all timer units will implicitly have - dependencies of type Requires= and - After= on sysinit.target, - a dependency of type Before= on - timers.target, as well as - Conflicts= and Before= on - shutdown.target to ensure that they are - stopped cleanly prior to system shutdown. Timer units with at - least one OnCalendar= directive will have an - additional After= dependency on - timer-sync.target to avoid being started - before the system clock has been correctly set. Only timer units - involved with early boot or late system shutdown should disable - the DefaultDependencies= option. + Unless DefaultDependencies= in the [Unit] section is set to + , all timer units will implicitly have dependencies of type Requires= and + After= on sysinit.target, a dependency of type Before= + on timers.target, as well as Conflicts= and Before= on + shutdown.target to ensure that they are stopped cleanly prior to system shutdown. Timer units + with at least one OnCalendar= directive will have an additional After= + dependency on timer-sync.target to avoid being started before the system clock has been + correctly set. Only timer units involved with early boot or late system shutdown should disable the + DefaultDependencies= option. -- cgit v1.2.3-54-g00ecf From 07bd0e02ef6395d1a57ce948ee427300b5284aff Mon Sep 17 00:00:00 2001 From: Evgeny Vereshchagin Date: Sat, 23 Apr 2016 03:49:47 +0300 Subject: man: document the default for systemd.timer's Persistent flag (#3099) Closes #3096 --- man/systemd.timer.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'man/systemd.timer.xml') diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 22c83f790f..eb0afee141 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -253,7 +253,8 @@ during the time when the timer was inactive. This is useful to catch up on missed runs of the service when the machine was off. Note that this setting only has an effect on timers - configured with OnCalendar=. + configured with OnCalendar=. Defaults + to false. -- cgit v1.2.3-54-g00ecf From 14e2baa369b120788322e727ecdd249127a13fa1 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 29 Apr 2016 13:36:38 +0200 Subject: man: document that RemainAfterExit= doesn't make much sense for repetitive timers Fixes #3122 --- man/systemd.timer.xml | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'man/systemd.timer.xml') 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 @@ foo.timer activates a matching service foo.service. The unit to activate may be controlled by Unit= (see below). + + 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 RemainAfterExit= 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. -- cgit v1.2.3-54-g00ecf From 2374374499f50939a769725c273c797d02dd4873 Mon Sep 17 00:00:00 2001 From: Andre Klärner Date: Mon, 16 May 2016 03:40:52 +0200 Subject: man: fix typo (#3261) --- man/systemd.timer.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'man/systemd.timer.xml') diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 0d0cccf152..0fa95e97a8 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -288,7 +288,7 @@ starting a timer unit that only elapses once: if RemainAfterElapse= is on, it will not be started again, and is guaranteed to elapse only once. However, - if RemainAfterLeapse= is off, it might be + if RemainAfterElapse= is off, it might be started again if it is already elapsed, and thus be triggered multiple times. Defaults to yes. -- cgit v1.2.3-54-g00ecf