On Mon, 30 Jan 2006, Simon Arlott <[EMAIL PROTECTED]> wrote
$ ntpq -c readvar ntp2.npl.co.uk status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg, processor="unknown", system="arm-wrs-vxworks", leap=00, stratum=2, precision=-9, rootdelay=9.277, rootdispersion=10.585, peer=37733, refid=78.84.80.0, reftime=c788d461.ee147ae1 Mon, Jan 30 2006 18:07:29.930, poll=6, clock=c788d489.91eb851e Mon, Jan 30 2006 18:08:09.570, state=4, phase=-9.595, frequency=4339962.464, jitter=4.230, stability=10.844
Wow. I thought ntpd had a 500 max for that. I've run ntpd on machines with dodgy clocks and found that what happens is the frequency maxes out at 500 and the clock is adjusted in whacking great steps every so often.
Certainly looks like there is something unusual, if not just wrong, about NPL's set up. Out of curiosity, I've added them to the config on one of my servers and started monitoring the offsets at
<http://rupert.raggedstaff.net/status/offsets.php> -- Chris Hastie _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
