On Mon, Nov 09, 2009 at 10:02:03AM -0500, Shoppa, Tim wrote: > Kai writes: > > we're using chrony to sync our servers. > > I think the problem is chrony and its lack of a good peer selection/outlier > rejection. > > You had three servers configured and for some reason chrony decided to use > one that was giving it bad time, when in all likelihood the other two had > good time.
Chrony has a source selection algorithm, it may not be as good as the one in ntpd, but it definitely should be able to throw away a falseticker. What version of chrony is the reporter running? -- Miroslav Lichvar _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
