shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-22 13:33:56 +03:00
Code

man: add <option> around default booleans in systemd.timer

Browse Source
This commit is contained in:
Anita Zhang 2020-10-30 16:16:31 -07:00
parent d3dcf4e3b9
commit 5cecbae158
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man/systemd.timer.xml
View File

@ -276,7 +276,7 @@
when the system clock (<constant>CLOCK_REALTIME</constant>) jumps relative to the monotonic clock
(<constant>CLOCK_MONOTONIC</constant>), or when the local system timezone is modified. These options
can be used alone or in combination with other timer expressions (see above) within the same timer
unit. These options default to false.</para></listitem>
unit. These options default to <option>false</option>.</para></listitem>
</varlistentry>
<varlistentry>
@ -301,7 +301,7 @@
is nonetheless subject to the delay imposed by <varname>RandomizedDelaySec=</varname>.
This is useful to catch up on missed runs of the service when the system was powered down. Note that
this setting only has an effect on timers configured with <varname>OnCalendar=</varname>. Defaults to
<varname>false</varname>.</para>
<option>false</option>.</para>
<para>Use <command>systemctl clean --what=state …</command> on the timer unit to remove the timestamp
file maintained by this option from disk. In particular, use this command before uninstalling a timer
@ -317,7 +317,7 @@
from suspend, should it be suspended and if the system supports this. Note that this option will only
make sure the system resumes on the appropriate times, it will not take care of suspending it again
after any work that is to be done is finished. Defaults to
<varname>false</varname>.</para>
<option>false</option>.</para>
<para>Note that this functionality requires privileges and is thus generally only available in the
system service manager.</para>
@ -343,7 +343,7 @@
<varname>RemainAfterElapse=</varname> is on, starting the timer a second time has no effect. However,
if <varname>RemainAfterElapse=</varname> 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
<varname>yes</varname>.</para></listitem>
<option>true</option>.</para></listitem>
</varlistentry>
</variablelist>
</refsect1>