summaryrefslogtreecommitdiffstats
path: root/man/systemd.special.xml
diff options
context:
space:
mode:
authorAlexander Batischev <eual.jp@gmail.com>2020-12-19 12:17:49 +0100
committerGitHub <noreply@github.com>2020-12-19 12:17:49 +0100
commit1431b2f701f7ba71e5d8664e709b1fad26797918 (patch)
treea1e6fd4981544efe881511461b96f6d6cf516c5d /man/systemd.special.xml
parenttmpfiles: fix typo (diff)
downloadsystemd-1431b2f701f7ba71e5d8664e709b1fad26797918.tar.xz
systemd-1431b2f701f7ba71e5d8664e709b1fad26797918.zip
man: Advertise systemd-time-wait-sync.service more (#17729)
* man: Advertise systemd-time-wait-sync.service more The description of time-sync.target says that NTP services *should* pull that target, but doesn't mention that e.g. systemd-timesyncd.service doesn't actually do that. As a result, time-sync.target is reached way earlier than people expect; see #5097, #8861, #11008. systemd provides systemd-time-wait-sync.service to ameliorate this problem, but doesn't feature it prominently in relevant manpages. In fact, it's only mentioned in passing in systemd-timesyncd.service(8). As a result, I ended up re-implementing that service, and I'm not the first one: https://github.com/NixOS/nixpkgs/pull/51338 This patch adds a mention right in the description of time-sync.target, which will hopefully raise awareness of this helper service.
Diffstat (limited to '')
-rw-r--r--man/systemd.special.xml11
1 files changed, 10 insertions, 1 deletions
diff --git a/man/systemd.special.xml b/man/systemd.special.xml
index a70e9ee0ca..1977157f9e 100644
--- a/man/systemd.special.xml
+++ b/man/systemd.special.xml
@@ -1018,7 +1018,16 @@
in. systemd automatically adds dependencies of type
<varname>After=</varname> for this target unit to all SysV
init script service units with an LSB header referring to
- the <literal>$time</literal> facility. </para>
+ the <literal>$time</literal> facility, and also to all timer
+ units with at least one <varname>OnCalendar=</varname>
+ directive. </para>
+
+ <para>This target might get reached before the clock is actually synchronized to an accurate reference
+ clock. To prevent that, enable
+ <citerefentry><refentrytitle>systemd-time-wait-sync.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+ if you're using
+ <citerefentry><refentrytitle>systemd-timesyncd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
+ or an equivalent service for other NTP implementations.</para>
</listitem>
</varlistentry>
</variablelist>