Heyho! On Wednesday 07 October 2009 21.00:51 PGNet Dev wrote: > how does one evaluate if ntp's functioning ok or not? some > combination of data & vehavior over time, i'm sure ...
Problem is: "function" in ntp is not binary.
One definition of "function" would be "achieve sync", which your ntpd seems
to do just fine: one clock has a '*', some have '+' and '-'. So this ntpd
is ready to give out its idea of time to the other hosts.
BUT. As you noticed, it's not a good clock. Think relativity: jitter is
what your ntpd "thinks" the other clocks are doing, or vice versa: it's a
question of interpretation. Obviously, the fact that all your reference
clocks are jumping around makes it likely that in reality your clock jumps
around, not all the others...
The best way to get some idea of the quality of your clock is to take a
known good ntp server and look what it says if it is asked to sync to your
questionable one (in addition to four or five others.)
(OTOH in such an extreme case, just get that clock fixed first. It's
obvious enough something is wrong. And finding out what, exactly, is wrong
is HARD.)
It might be the hardware. It might as well be that Xen does funny stuff
with the interrupts. virtualisation is complex, and remember: even the Dom0
runs under the control of the hypervisor, same as DomUs, it just has special
rights.
cheers
-- vbi
--
To create encryption keys, RSA uses two huge prime numbers and multiplies
them together to produce an even bigger prime.
-- Sandeep Junnarkar at news.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
