Eugene Smiley wrote: > Everywhere you read the documentation, it suggests that you pick a > set of servers "near" you. Mostly they leave it up to you to > figure out what that means, some go as far as saying "near to you > using PING or TRACEROUTE." This still leaves NEAR as being a vague > term (maybe is should be, I don't know). > > I'm suggesting that we could each use noselect to monitor our > NEAREST pool servers based on an ascending sort on delay. It would > require a script to be run on the "ntpq -p" output(I have a rough > one in the works), and maybe some graphing to see the results over > time...
Ok. So, I wrote the script. There are some things to know: - The script currently forces the user to manually update their ntp.conf file. I'd rather inconvenience people in the beginning than have this script easily DOS the pool or butcher someones ntp.conf file. The results print to the console, but they can be redirected to a file where it can be cut and pasted into ntp.conf. - You can end up monitoring all the pool ntp servers if you change the percentages, but I wouldn't recommend it for the average pool member. Even with the change in maxpoll, there is no way of knowing how all 370 pool members monitoring every server will impact the pool. - It's possible to get yourself KOD'd on servers by restarting ntp to frequently with this script. The script is located at: http://www.esmiley.net/ntp/ntpmonitor.txt and it's done in perl. Any and all feedback is appreciated. Now, to figure out RRDtools and get the graphing set up. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
