Hal Murray <[email protected]> wrote on Thu, 30 Mar 2017 at 13:43:34 -0700 in <[email protected]>:
> That should work too. I don't know much about the Mac environment. If it's > running a normal-enough ntpd it is already a server and you don't have to do > anything. If not, you will have to build/install your own and/or poke holes > in the firewall rules. It is worth noting that the ntpd that Apple ships is kind of bizarre, and it does not actually adjust the clock on the Mac. (Instead it writes to the drift file -- or at least it is supposed to -- and an Apple process called "pacemaker(8)" readthe drift file and tries to maintain the systme clock. In my experience (only through Yosemite -- 10.10) this mechanism was horribly broken and did not maintain my laptop's system clock in any useful way.) This probably doesn't actually affect the intended use (as the goal is to keep machines in sync, not to keep them accurate), but anyone who messes with ntpd under OS X should be aware that it is "weird." Building the stock ntpd under OS X works just fine, and I recommend that for anyone who wants to tinker with ntp under OS X. [email protected] John Hawkinson _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
