what was up with ntp again?

Chris Jones jonesc at hep.phy.cam.ac.uk
Mon Mar 23 11:23:44 PDT 2015

> On 23 Mar 2015, at 6:20 pm, Brandon Allbery <allbery.b at gmail.com> wrote:
>> On Mon, Mar 23, 2015 at 2:17 PM, Chris Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>> > The default permissions are likely to be fine:
>> >
>> > -rw-r--r-- 1 root wheel 9 Dec 24 02:58 /var/db/ntp.drift
>> That file hasn't been updated for a while ?
> That would be correct for the Apple ntpd/pacemaker setup. It's created once and not updated thereafter, which is the root of the usual problem --- real ntpd will adjust the drift when it changes, Apple's does not, and new machines will usually see changes in their clock drift as they settle in. And the fix is to remove the out of date one, run Apple ntpd or full ntpd without pacemaker running to let it create a more up to date one, and then restart pacemaker, as I described originally.

So why was mine seemingly updated only yesterday ? I've never done anything w.r.t. ntp or pacemaker on this machine, so whatever setting is running it must by definition be the default Apple setup ... ?

> -- 
> brandon s allbery kf8nh                               sine nomine associates
> allbery.b at gmail.com                                  ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20150323/6125404a/attachment.html>

More information about the macports-users mailing list