[email protected] said: > Problem #1 seems to be due to the fact that rawstats pertains to client/ > server based synchronization. I was only using a GPS clock to sync, so > after adding another www based NTP server, rawstats was generated.
rawstats only works for network systems. clockstats might do what you want. (What it records depends upon which refclock driver you are using.) > However I'm still unsure why peerstats does not update when the offset is > outside of a certain (currently undetermined) range. In the mean time I > think I'll just write a script that records the offset from ntpq -p and logs > it into a file once every few seconds. However I really want to pull this > information from peerstats. If you have another system running ntpd, you can use its rawstats to monitor other systems. Just add something like this to your config file: server xxxx noselect minpoll xx maxpoll xx -- These are my opinions. I hate spam. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
