It was my understanding the time monitoring was only to make sure your
server was relatively accurate. It wasn't designed to be a perfect
monitor for your server.
On 9/25/2013 1:21 PM, AlbyVA wrote:
Ahhh okay. So maybe I'm expecting too much perfection of the
monitoring server and
it's plotting of offset data.
-Alby
On Wed, Sep 25, 2013 at 1:17 PM, Rob Janssen <[email protected]
<mailto:[email protected]>> wrote:
AlbyVA wrote:
"...A couple of times an hour the pool system checks the time
from your server and compares it to the local time..."
I was wondering, where is "local time" being obtained? Is it
an average of all the other servers in a Country? All I see
is a monitoring station being in Los Angeles.
Thanks,
-Alby
It probably is the local time on the monitoring server.
Not "local time" in the sense of the local wall clock time, but
UTC time locally on the server.
All of the ntp server works in UTC time, local time is not a
concept known to ntp.
Conversion of UTC to local time is done by the operating sytem
and/or library routines.
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.
Rob
_______________________________________________
pool mailing list
[email protected] <mailto:[email protected]>
http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
