Add Persistent=true to systemd.timer #60

floli · 2018-05-17T19:50:23Z

floli commented

2018-05-17 19:50:23 +00:00

Persistent=

    Takes a boolean argument. If true, the time when the service unit was last
triggered is stored on disk. When the timer is activated, the service unit is
triggered immediately if it would have been triggered at least once 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=. Defaults to false.

If a daily backup was missed, the backup should be started immediately and not wait for the next daily invocation (when the machine might be switched off again).

``` Persistent= Takes a boolean argument. If true, the time when the service unit was last triggered is stored on disk. When the timer is activated, the service unit is triggered immediately if it would have been triggered at least once 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=. Defaults to false. ``` If a daily backup was missed, the backup should be started immediately and not wait for the next daily invocation (when the machine might be switched off again).

witten closed this pull request

2018-05-21 05:18:13 +00:00

witten commented

2018-05-21 05:18:41 +00:00

Thanks for taking the time to add this! Makes sense.

witten referenced this issue from a commit

2018-05-21 05:20:42 +00:00

Add "Persistent" flag to systemd timer example. (#60)

witten referenced this issue from a commit

2023-03-25 06:47:39 +00:00

Allow defining custom variables in config file (#612).

Sign in to join this conversation.