[systemd-devel] Upstream service file for NTP daemon chrony

[David Strauss]

On Mon, Jul 2, 2012 at 3:44 PM, Paul Menzel
<paulepanter at users.sourceforge.net> wrote:
>> > daemon actually finds a NTP server.
>>
>> Also, is this necessary? Can't chronyd just fail to sync NTP until it
>> works? There's value to an NTP daemon running even if it lacks
>> upstream sync sources for a while.
>
> Which? But it might be true.

Two sections of the FAQ [1] [2] detail a couple reasons. In
particular, NTP daemons like Chrony compensate for previously
identified clock skew even when an external clock is unavailable.
Also, Chrony can serve as an NTP server for remote or local (say, VM)
applications that would benefit from Chrony connectivity. For these
two reasons at a minimum, Chrony should run regardless of upstream
connectivity.

[1] http://chrony.tuxfamily.org/FAQ.html#question_2.1
[2] http://chrony.tuxfamily.org/FAQ.html#question_4.1

-- 
David Strauss
   | david at davidstrauss.net
   | +1 512 577 5827 [mobile]