Simon Arlott wrote: > Niek wrote: >> On 1/30/2006 7:12 PM +0100, Simon Arlott wrote: >> >>> The frequency status variable is ridiculously high: >> >> >> Maybe becasue something is funky elsewhere (check reach): >> > > Isn't the frequency variable directly related to local clock drift?
Yes - it represents the amount of adjustment to the local clock - it will be different on every machine - if it's very low it just means that the local clock was pretty accurate before ntp started to manage it. It doesn't tell you anything about the stability of the clock (at least not as a single snapshot). Changes in frequency through the day will normally paint a good picture of the temperature shifts the machine is experiencing. John > > > ------------------------------------------------------------------------ > > _______________________________________________ > timekeepers mailing list > [email protected] > https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers > _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
