blob: feb394da894e56c0facba91dcbfe1203fb6f326a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
From 1d83dac5adba9e1db5b058436e23ba7ac403d652 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
Date: Mon, 7 Apr 2014 20:58:37 -0400
Subject: [PATCH 3/4] man: reword Persistent= description
I think it is easier to grok this way.
---
man/systemd.timer.xml | 26 ++++++++++++--------------
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 58eaab0..44f55e0 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -255,20 +255,18 @@
<term><varname>Persistent=</varname></term>
<listitem><para>Takes a boolean
- argument. If true the service unit is
- immediately triggered when the timer
- unit is activated and the timer
- elapsed at least once since the last
- time the service unit has been
- triggered by the timer unit. The time
- when the service unit was last
- triggered is stored on disk. This is
- useful to catch up for missed timers
- when a machine is shutdown temporarily
- and then is powered up again. Note
- that this setting only has an effect
- on timers configured with
- <varname>OnCalendar=</varname>.
+ 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 <varname>OnCalendar=</varname>.
</para></listitem>
</varlistentry>
--
1.9.2
|
