Rob Janssen kirjoitti:
Anyway, there is an error in this monitoring. The monitored time always
has a negative offset.
I have never seen anything different, no matter how correctly tuned my
time server.
(it should now be within .1 ms most of the time, but the monitoring plot
cloud is always
between -10 and -3 ms)
I would say there is a systematic error of about 4 or 5 ms.
The reason for this is most probably asymmetric routing -- the packets
TO your server are routed through some other route than the packets FROM
your server. This is perfectly normal, nothing to worry about.
If you have a look at my graphs at http://www.pool.ntp.org/user/avij ,
you'll notice that most them don't look perfect either. I've long ago
stopped caring too much about the graphs. Those servers still provide
reasonably accurate time to the pool users, despite the funny-looking
graphs.
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
