[email protected] said: > Hi, all. I'm curious what folks are doing for monitoring/reporting on their > own ntpd hosts with respect to client connections, accuracy, etc? ...
ntpd can generate lots of data if you turn on the statistics stuff. Details are in monopt.html sysstats will give you an hourly summary of traffic. loopstats will give you data on what this server thinks about its clock. peerstats will give you a filtered view of the data from one server. rawstats will give you the unfiltered data. If you look at the peerstats/rawstats data and you see that all the servers are off in the same direction, your server is probably off in the other direction. Or maybe you have buffer bloat. If you see one server that is consistently off significantly you may be seeing asymmetric routing. This is more likely on long paths. If you assume that your clock and the clock on the remote server are both accurate, then you can get the network delays in both directions from the rawstats. -- These are my opinions. I hate spam. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
