Auto selection of geographically appropriate time server

[wilsonmar]

This is not a big thing, as argued by http://blogs.n1zyy.com/n1zyy/2008/04/29/long-distance-ntp/

I am talking about the geo-specific public_ntp="north-america.pool.ntp.org" in the install.sh script https://github.com/nginxinc/nginx-amplify-agent/raw/master/packages/install.sh

I assume the script is invoked by people around the world. I didn't look into the script very precisely, but is there logic to identify an ntp server appropriate to the server's time zone and take advantage of the rotating pool of low-stratum NTP servers as in 0.europe.pool.ntp.org as noted in a driftfile in http://www.pool.ntp.org/en/use.html

It's just one less nit OCD sysadmins worry about when automating "everything".

http://doc.ntp.org/3-5.93e/ntpdate.html says: "ntpdate sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the server arguments to determine the correct time."

http://help.fortinet.com/coyotepoint/10-3-2/Content/NetConfig/Selecting_an_NTP_Server.htm