chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
core: --user -- add basic.target an sort against it like --system does
[elogind.git]
/
man
/
systemd.timer.xml
diff --git
a/man/systemd.timer.xml
b/man/systemd.timer.xml
index 484287ccf67fc3f770f6883e8f7df6039e8b4d3e..bb3a6d138650d18e262a716ed284c7bb8db17802 100644
(file)
--- a/
man/systemd.timer.xml
+++ b/
man/systemd.timer.xml
@@
-141,7
+141,7
@@
also include time units. Example:
"OnBootSec=5h 30min" means 5 hours and
30 minutes after boot-up. For details
also include time units. Example:
"OnBootSec=5h 30min" means 5 hours and
30 minutes after boot-up. For details
- about the syntax of time spans see
+ about the syntax of time spans
,
see
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<para>If a timer configured with
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<para>If a timer configured with
@@
-165,8
+165,8
@@
assignments will have no
effect.</para>
assignments will have no
effect.</para>
- <para>Note that timers
are
not
- necessarily expire
d
at the precise
+ <para>Note that timers
do
not
+ necessarily expire at the precise
time configured with these settings,
as they are subject to the
<varname>AccuracySec=</varname>
time configured with these settings,
as they are subject to the
<varname>AccuracySec=</varname>
@@
-182,13
+182,13
@@
event expressions. See
<citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>
for more information on the syntax of
event expressions. See
<citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>
for more information on the syntax of
- calendar event expressions. Otherwise
+ calendar event expressions. Otherwise
,
the semantics are similar to
<varname>OnActiveSec=</varname> and
related settings.</para>
the semantics are similar to
<varname>OnActiveSec=</varname> and
related settings.</para>
- <para>Note that timers
are
not
- necessarily expire
d
at the precise
+ <para>Note that timers
do
not
+ necessarily expire at the precise
time configured with this setting,
as it is subject to the
<varname>AccuracySec=</varname>
time configured with this setting,
as it is subject to the
<varname>AccuracySec=</varname>
@@
-201,7
+201,7
@@
<listitem><para>Specify the accuracy
the timer shall elapse with. Defaults
to 1min. The timer is scheduled to
<listitem><para>Specify the accuracy
the timer shall elapse with. Defaults
to 1min. The timer is scheduled to
- e
xpir
e within a time window starting
+ e
laps
e within a time window starting
with the time specified in
<varname>OnCalendar=</varname>,
<varname>OnActiveSec=</varname>,
with the time specified in
<varname>OnCalendar=</varname>,
<varname>OnActiveSec=</varname>,
@@
-211,7
+211,7
@@
<varname>OnUnitInactiveSec=</varname>
and ending the time configured with
<varname>AccuracySec=</varname>
<varname>OnUnitInactiveSec=</varname>
and ending the time configured with
<varname>AccuracySec=</varname>
- later. Within this time window the
+ later. Within this time window
,
the
expiry time will be placed at a
host-specific, randomized but stable
position, that is synchronized between
expiry time will be placed at a
host-specific, randomized but stable
position, that is synchronized between
@@
-220,7
+220,7
@@
in networked installations, as well as
optimizing power consumption to
suppress unnecessary CPU wake-ups. To
in networked installations, as well as
optimizing power consumption to
suppress unnecessary CPU wake-ups. To
- get best accuracy set this option to
+ get best accuracy
,
set this option to
1us. Note that the timer is still
subject to the timer slack configured
via
1us. Note that the timer is still
subject to the timer slack configured
via
@@
-229,7
+229,7
@@
setting. See
<citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
for details. To optimize power
setting. See
<citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
for details. To optimize power
- consumption make sure to set this
+ consumption
,
make sure to set this
value as high as possible and as low
as necessary.</para></listitem>
</varlistentry>
value as high as possible and as low
as necessary.</para></listitem>
</varlistentry>