Hi, On 16/06/2012 21:40, "Shoppa, Tim" <[email protected]> wrote: > Chuck, > > You know ntpd (via ntpq -c peers) does a dang good job of monitoring the > statistics of your time sources. > > ntpq -c peers shows the sort of statistics that a long-lived client expects > to be of high quality. Offset, delay, and jitter are very important to the > ntpd algorithms, and it tracks these very meticulously. > > I would advise, that ntpq -c peers is what you want to be looking at. >
This however does not output your scoring or accuracy according to the NTP Pool website as the website uses different mechanisms than are available locally. What I would advise perhaps instead is use the csv log and generate graphs/data renderings locally instead of depending on the graphs that can change format easily. the CSV logs are available as such: http://www.pool.ntp.org/scores/72.38.129.202/log?limit=50 (obviously replacing your time server's address in place) -- Kradorex Xeron <[email protected]> Founder, Executive Director Digibase Operations, Research and Development
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
