On Tue, Mar 08, 2011 at 05:00:44PM +0000, unruh wrote:
> >>>> filtoffset= 67671.8 66534.8 65931.3 65118.0 63317.3 63029.5 62216.4 
> >>>> 58156.6,

> Not at all sure how Mills comes into the picture. On a system where the
> frequency fluctuates wildly, ntpd is not the right answer, nor is any
> system. I suspect that the best you could do would be to run something
> like ntpdate often and jump the clock around.

The frequency offset in this case seems to be around 2% which is still
well below the 10% maximum Linux can adjust. I'd try chrony before
resorting to ntpdate, the timekeeping probably won't be very good, but
at least the clock won't be stepped.

-- 
Miroslav Lichvar
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Reply via email to