Re: Problems with ntp
In gmane.linux.debian.devel.release Steve Langasek <firstname.lastname@example.org> wrote:
> What are you going to replace it with? AFAIK, ntp is the only package
> we have in Debian which supports useful clock synchronization, which is
> essential for a number of other services (e.g., Kerberos).
Well, there is chrony, which is feature complete with ntp as far as I
can tell. Even without the licensing issues, I would recommend chrony
anyway: chrony converges to the time servers much faster than ntp. I
have long suspected that there is something wrong with the ntp
phase-lock loop algorithm (the clock is rate-adjusted to somewhere close
to the time server after some hours, and then diverges again ...), but
email exchange with Dr. Mills reaches nowhere. He is convinced that he
is right, but I am convinced that there is something wrong after I look
closely into the logs.
Clock synchronization work much better with chrony. I just installed a
new Debian box, and chrony brings the server from 87 seconds offset to
steady 50us offset, -21.9 ppm frequency adjustment within an hour
(with a stratum-2 server on campus network).