Re: Linux 2.6.29-rc6

[john stultz]

On Tue, 2009-03-03 at 21:39 +0100, Jesper Krogh wrote:
> john stultz wrote:
> > Do you see the same behavior if you drop all but one server (including
> > the local clock: 127.127.1.0)? 
> 
> Yes.
> Mar  3 21:20:59 quad12 ntpd[2435]: ntpd 4.2.4p4@xxxxxxxx Tue Jan  6 
> 15:50:55 UTC 2009 (1)
> Mar  3 21:20:59 quad12 ntpd[2436]: precision = 1.000 usec
> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #0 wildcard, 
> 0.0.0.0#123 Disabled
> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #1 wildcard, 
> ::#123 Disabled
> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #2 lo, ::1#123 
> Enabled
> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #3 bond0, 
> fe80::21e:68ff:fe57:8169#123 Enabled
> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #4 lo, 
> 127.0.0.1#123 Enabled
> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #5 bond0, 
> 10.194.132.91#123 Enabled
> Mar  3 21:20:59 quad12 ntpd[2436]: kernel time sync status 0040
> Mar  3 21:20:59 quad12 ntpd[2436]: frequency initialized -29.286 PPM 
> from /var/lib/ntp/ntp.drift
> Mar  3 21:21:58 quad12 ntpd[2436]: synchronized to 10.194.133.12, stratum 4
> Mar  3 21:21:58 quad12 ntpd[2436]: time reset -6.148275 s
> Mar  3 21:21:58 quad12 ntpd[2436]: kernel time sync status change 0001
> Mar  3 21:25:01 quad12 ntpd[2436]: synchronized to 10.194.133.12, stratum 4
> Mar  3 21:37:03 quad12 ntpd[2436]: time reset -0.664351 s
> 
> Only one server and the minpoll 4 maxpoll 4 options to the server line.

Well, it may still need a few hours to settle. :)  Again, those time
resets are seen when NTPd doesn't have a good drift ppm at startup, and
it has to find it.

thanks
-john

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/