| Re: [chrony-dev] handling of unstable sources |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Mon, Jul 12, 2010 at 04:52:47PM +0200, Frank Muzzulini wrote:
> Miroslav Lichvar wrote:
> >Interesting. Maybe the 1ms resolution is causing chrony to think it's
> >following the source very well for short intervals. The statistics and
> >measurements logs would help.
>
> I repeated the test, so here you are. I also included tracking and
> /var/log/messages (timestamps there are UTC+2)
>
> At first chronyd synchronised to 10.10.9.13 and from 11:33:35 to
> 11:36:15 it was very well synchronised to that one. Then in 11:36:17
> it suddenly chosed to prefer 10.10.9.14 and only choosed 10.10.9.13
> once again afterwards.
Ok, it's exactly as you said, 10.10.9.14 is almost always prefered
because it reports zero root dispersion. And when it makes the 5ms
correction it may be marked as jittery and 10.10.9.13 will be selected
as it's the only selectable source.
--
Miroslav Lichvar
---
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.