[ntp:questions] Flash 400 on all peers; can't get ntpd to be happy

Chris Albertson albertson.chris at gmail.com
Tue Mar 8 16:15:24 UTC 2011

On Tue, Mar 8, 2011 at 1:16 AM, Miroslav Lichvar <mlichvar at redhat.com> wrote:
> On Sun, Mar 06, 2011 at 11:22:34AM +0000, David Woolley wrote:

> This seems to be a common problem and with virtual machines getting
> everywhere it will probably only get worse. I'm wondering how hard it
> would be for ntpd to detect that the clock frequency is outside the
> acceptable range and write a "your clock is broken" message to syslog?

It's the old joke again:  Man who has one clock knows what time it is.
 A man with two clocks is not sure.   How is ntpd to know the PCs
clock is not good unless there are enough clocks that it can apply
something like it's clock selection algorithm.   You need a minimum of
two lus the PC's

ntpd would need to see a set of servers that track each other well but
as a group "bounce around". Then it could deduce that it was bouncing,
not the set.
Chris Albertson
Redondo Beach, California

More information about the questions mailing list