Re: [chrony-dev] handling of unstable sources

2010-07-14 Thread Miroslav Lichvar
On Wed, Jul 14, 2010 at 02:08:43PM +0200, Frank Muzzulini wrote: > I also noticed that even directly after an update the server reports > a root dispersion of ~0.5ms. I don't know however whether this is a > general feature of ntpd or it is a configured value trying to > reflect the potential

Re: [chrony-dev] handling of unstable sources

2010-07-14 Thread Frank Muzzulini
Miroslav Lichvar wrote: How do you define reasonable? :) The root dispersion value in NTP packet has only about 15us resolution. Ntpd assumes a fixed frequency error and adds to the dispersion 15 us every second since last reference update, but chrony uses the estimated skew instead, so with a

Re: [chrony-dev] handling of unstable sources

2010-07-13 Thread Frank Muzzulini
Miroslav Lichvar wrote: 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. So Mills' conservative