Jan writes: > Uninteresting to you maybe, but it is the answer to Tims question: > "don't use the pool stats to monitor your own server". > That's the point you missed.
I know (and most, but not all, server maintainers know) that it is monitoring not just the server, but the asymmetric latency between the server and the monitoring site. Of course there are millions of TCP/IP addresses, so really the grand latency matrix consists of millions times millions of numbers at any point in time, but having just a single measure of a route is better than nothing! (In fact there are other global projects to measure WAN latencies, and most of them use ntpd with a local refclock to get timing resolutions in the microsecond range... with some provisos! Lotsa little things pop up once you expect to do this good.) If, like ntpd, the monitoring site also plotted round-trip-time as a function of time of day, it would be even more useful. Tim. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
