<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Nov 22, 2014 at 10:01 AM, René J.V. <span dir="ltr"><<a href="mailto:rjvbertin@gmail.com" target="_blank">rjvbertin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Out of curiosity, what's wrong with the system's ntp?</blockquote></div><br>For what it's worth, starting with 10.8 I've been seeing the clock go out of sync a lot. On my current 10.9 the system usually ends up 2 minutes ahead of my other ntp-synced devices.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I've been watching on my 10.9 to see what it is doing. It seems like it initially locks to the servers the way I'd expect, and then lets go of it and every 10 minutes checks whether it's near the server time and if it's far enough out it resyncs just enough to fi the time and then desyncs again, apparently deliberately. (As seen in mtpq -p: "reach" eventually reaches 377, stays there for about 5 minutes, then drops to 1 and stays there. "when" afterward counts up to somewhere a little over 1000 with offset and jitter not changing, then they change and "when" resets.)</div><div class="gmail_extra"><br></div><div class="gmail_extra">I am rather tempted to switch to ports ntpd myself, watching this. But it looks like Apple's ntpd is the normal one and not one of the alternatives that don't condition the clock fully (openntpd, various sntp implementations)? It's just not behaving like I expect ntpd to behave.<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>