diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-04-07 20:58:37 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-04-07 21:02:47 -0400 |
| commit | de41590a9bb370de92e4a1ed933bc6e38abb6787 (patch) | |
| tree | 00d644bdbcfdb8f6fdff7407845d6bbddb408587 | |
| parent | c4acff1275e8d3a1c29c9b417b93f6cf6f10e258 (diff) | |
man: reword Persistent= description
I think it is easier to grok this way.
| -rw-r--r-- | man/systemd.timer.xml | 26 |
1 files changed, 12 insertions, 14 deletions
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 58eaab09f8..44f55e05e3 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> |