Hi all, I joined the pool a few months ago when I set up NTP on a webserver and realized I might as well have it help out the community. I've got a few questions I've acquired over the past few months, which I'll batch together here.
- I'm setting up a new server on the East Coast (US). I'm trying to find some NTP servers that are close (latency-wise), but many of them block ping. Short of adding them to my ntp.conf and restarting, is there a way to test their response time? - A related question: is there a way to modify my server list while the server's running? Halting ntpd, editing the ntpd.conf, and then restarting ntpd is problematic, especially when it takes several minutes for it to get a "fix" upon restarting. - I've never seen a good explanation for when it's appropriate to use the burst/iburst keywords, so I've assumed that it's not appropriate for me to be using them. (My current server is Stratum 2, so I'm particularly worried about placing too much of a load on S1 servers.) Should I leave my settings as-is, or does it makes sense to add them to speed up its resuming service after restarting? (Which is rare.) - Is support.ntp.org consistently (very) slow to load for everyone, or just me? Is this a situation we can help out with somehow? - When I set up my server in Texas, there were ample stratum 1 servers with open access policies, allowing me to become a stratum 2 without problems. However, it seems that there are fewer open stratum 1s on the East Coast... Is running a server in the pool considered a good reason to request permission, or should I just stay at stratum 3? Thanks for the help! -- Matt (72.36.178.234)
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
