Re: [chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 2.0-13-g0abdc2a

[Bill Unruh <unruh@xxxxxxxxxxxxxx>]

William G. Unruh   |  Canadian Institute for|     Tel: +1(604)822-3273
Physics&Astronomy  |     Advanced Research  |     Fax: +1(604)822-5324
UBC, Vancouver,BC  |   Program in Cosmology |     unruh@xxxxxxxxxxxxxx
Canada V6T 1Z1     |      and Gravity       |  www.theory.physics.ubc.ca/

> - Log -----------------------------------------------------------------
> commit 0abdc2a35042f70449d662f96d7c39911371d188
> Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
> Date:   Tue Jun 2 13:24:04 2015 +0200
>
>     smooth: add option to smooth out only leap seconds
>
>     The leaponly option can be used to enable a mode where only leap seconds
>     are smoothed out and normal offset/frequency changes are ignored. This
>     is useful to make the interval in which a leap second is smoothed out
>     constant and allow an NTP client to use multiple leap smearing servers
>     safely.
I am very uncomfortable with these kinds of leap smoothing procedures. In
particular, since there is no standard as to the smoothing, this risks
instability as a whole variety of "smoothed" servers all fight each other in
trying to control the time.  I think before heading down this path, we need an
rfc to both standardize the smoothing, and a flag to warn clients that that server is
smoothing. chrony and ntpd claim acccuracies down to microseconds, and here we
are degrading that by 6 orders of magnitude to 1/2 second scales. While of
course if your system is an endpoint and not serving anyone else, it does not
matter, but this will be applied to servers.

--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.