Nate Bargmann <n0nb@???> writes:
> SD now includes a replacement for running ntp/ntpdate to synchronize
> time so that is being absorbed.
According to information 'from the internet', that's an SNTP client and
While a full featured NTP server or -client reaches a very high
level of accuracy and avoids abrupt timesteps as much as
possible by using different mathematical and statistical methods
and smooth clock speed adjustments, SNTP can only be recommended
for simple applications, where the requirements for accuracy and
reliability are not too demanding.
By disregarding drift values and using simplified ways of system
clock adjustment methods (often simple time stepping), SNTP
archieves only a low quality time synchronization when compared
with a full NTP implementation.
https://www.meinbergglobal.com/english/faq/faq_37.htm
This then (finally!) achieves something certain people have been pushing
for for a long time, namely, it renders the 'wallclock' useless for
sychronizing operations of distributed systems by turning it into a PRNG
(which may randomly jump backward and forward according to the whims of
the SNTP implementation).