No subject

<br>
launchctl unload /System/Library/LaunchDaemons/com.apple.pacemaker.plist<br=
>
/usr/libexec/pacemaker -d /var/db.local/pacemaker.drift -a 8 &amp;<br>
<br>
My hardware clock, when pacemaker is not running, according to the system n=
tp, is over -500. And with that error rate, ntp will not sync.<br>
<br>
So ... right now, I&#39;m trying to binary search, to find where the system=
 ntpd is happy. I tried -30, and the system ntpd was not happy (never went =
above 64 poll). But using the ports version of ntpd, it syncs happily (got =
up to 256 poll). Go figure.</blockquote><div><br></div><div>In fact, with a=
 pacemaker drift of -29, my machine synched with a poll of 1024, and a calc=
ulated drift of -1.784. In comparison, the system NTPD in the same setup ca=
lculated a drift of over -315, and stepped the clock daily. Never getting p=
ast poll 64.<br><br></div><div>I still cannot figure out why Apple wanted t=
o create &quot;pacemaker&quot; instead of just changing what constant was a=
dded to the system time every hardware tick. That seems to be the best &quo=
t;low-power&quot; solution -- just change the existing addition. <br></div>=
</div></div></div></div>

--001a11c34438c1fe30050988a173--