From 415f8a5bfed4604e4a1bc275682d51af3ad3b611 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 10 Sep 2020 19:08:45 +0200 Subject: man: document that RemainAfterElapse=no means that also the triggered unit needs to deactivate Fixes: #16378 --- man/systemd.timer.xml | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) (limited to 'man/systemd.timer.xml') diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 32ddb1c6e4..32f7814f8e 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -335,18 +335,14 @@ RemainAfterElapse= - Takes a boolean argument. If true, an elapsed - timer will stay loaded, and its state remains queryable. If - false, an elapsed timer unit that cannot elapse anymore is - unloaded. Turning this off is particularly useful for - transient timer units that shall disappear after they first - elapse. Note that this setting has an effect on repeatedly - 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 RemainAfterElapse= is off, it might be - started again if it is already elapsed, and thus be triggered - multiple times. Defaults to + Takes a boolean argument. If true, a timer will stay loaded, and its state remains + queryable even after it elapsed and the associated unit (as configured with Unit=, + see above) deactivated again. If false, an elapsed timer unit that cannot elapse anymore is unloaded + once its associated unit deactivated again. Turning this off is particularly useful for transient + timer units. Note that this setting has an effect when repeatedly starting a timer unit: if + RemainAfterElapse= is on, starting the timer a second time has no effect. However, + if RemainAfterElapse= is off and the timer unit was already unloaded, it can be + started again, and thus the service can be triggered multiple times. Defaults to yes. -- cgit v1.2.1