1
1
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-25 23:21:33 +03:00
systemd-stable/man/systemd-time-wait-sync.service.xml
Zbigniew Jędrzejewski-Szmek 11a1589223 tree-wide: drop license boilerplate
Files which are installed as-is (any .service and other unit files, .conf
files, .policy files, etc), are left as is. My assumption is that SPDX
identifiers are not yet that well known, so it's better to retain the
extended header to avoid any doubt.

I also kept any copyright lines. We can probably remove them, but it'd nice to
obtain explicit acks from all involved authors before doing that.
2018-04-06 18:58:55 +02:00

79 lines
2.8 KiB
XML

<?xml version='1.0'?> <!--*-nxml-*-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
SPDX-License-Identifier: LGPL-2.1+
This file is part of systemd.
Copyright 2018 Peter A. Bigot
-->
<refentry id="systemd-time-wait-sync.service" conditional='ENABLE_TIMESYNCD'>
<refentryinfo>
<title>systemd-time-wait-sync.service</title>
<productname>systemd</productname>
<authorgroup>
<author>
<contrib>Developer</contrib>
<firstname>Peter</firstname>
<surname>Bigot</surname>
<email>pab@pabigot.com</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta>
<refentrytitle>systemd-time-wait-sync.service</refentrytitle>
<manvolnum>8</manvolnum>
</refmeta>
<refnamediv>
<refname>systemd-time-wait-sync.service</refname>
<refname>systemd-time-wait-sync</refname>
<refpurpose>Wait Until Kernel Time Synchronized</refpurpose>
</refnamediv>
<refsynopsisdiv>
<para><filename>systemd-time-wait-sync.service</filename></para>
<para><filename>/usr/lib/systemd/systemd-time-wait-sync</filename></para>
</refsynopsisdiv>
<refsect1>
<title>Description</title>
<para><filename>systemd-time-wait-sync</filename> is a system service that delays the start of units that depend on
<filename>time-sync.target</filename> until <filename>systemd-timesyncd.service</filename> or something else has
set the system time and marked it as synchronized. Reaching this state generally requires synchronization with an
external source, such as an NTP server.</para>
<para>When this unit is not enabled the <filename>time-sync.target</filename> synchronization point may be reached
as soon as the system time is advanced by <filename>systemd-timesyncd.service</filename> to the time stored at the
last shutdown. That time may not meet the expectations of dependent services that require an accurate
clock.</para>
</refsect1>
<refsect1>
<title>Notes</title>
<para>This service works correctly with a time synchronization service like
<filename>systemd-timesyncd.service</filename> that uses the same protocol as NTP to set the time from a
synchronized source. When used with time synchronization services that follow a different protocol the event of
setting synchronized time may not be detected in which case this service will not complete.</para>
</refsect1>
<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd-timesyncd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
</para>
</refsect1>
</refentry>