| ||
Tue 2024-04-23
Fri 2024-04-19
Thu 2024-04-18
Mon 2024-04-15
Butterick’s Practical Typography Sat 2024-04-13
Fri 2024-04-12
Wed 2024-04-10
Boy Meets Boy Meets Boys’ Love Tue 2024-04-09
Mon 2024-04-08
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
I love NTP, the
magic Internet protocol that keeps computer clocks synchronized. One
of the nice things Apple does is run an NTP service for all their
computers. That's how your Mac always knows the right time. Here are
some notes on what they do.
My American MacOS 10.3.9 box has the following /private/etc/ntp.conf:
server time.apple.com minpoll 12 maxpoll 17
That means my Mac asks time.apple.com for the time somewhere between
once an hour and once every day and a half. That's less often
than usual for NTP, presumably an accuracy / scalability tradeoff.
time.apple.com currently resolves to 4 IP addresses, 17.254.0.26, .27, .28, and .31. All of them seem to be in San Jose, California. .26 is the most accurate clock (stratum 2), the others are just behind at stratum 3. Using ntpdc you can find out where .27 gets its time from. They're well synchronized, talking to several stratum 1 clocks. They poll each of those every 128 seconds, aggressive but maybe appropriate for such a well-used clock. They sync around the world, and also run services in Europe and Asia for their clients. |
|
