From: Rodolphe Pineau <pineau@rti-zone.org>

Date: October 5, 2009 12:39:45 AM MDT

To: Astro_IIDC@yahoogroups.com

Subject: Re: [Astro_IIDC] Re: Getting more accurate system clock times.



On Sun 10/4/09, at 23:18, milton_aupperle wrote:


Hi Rodolphe;


Actually I've found it's not a firewall issue and looks to be an OS X 10.5.8 issue.


If I have the "set date & Time Automatically" check box checked and I execute the "ntptrace" command in the terminal, it will work:


localhost: stratum 16, offset 0.000000, synch distance 0.000390


If I uncheck it and then use ntptrace, it timeouts because it isn't in auto mode.


It also will not allow you to use ntpdate if it's in Auto mode, and will return a socket in use error.


TTYL..


Milton Aupperle


It's because ntpdate can't run in ntpd is running (and ntptrace needs ntpd). When servers and desktop have to start ntpd, they usualy do a ntpdate first (it then retrieve the correct time and date from the ntp server specified in /etc/ntp.conf) and then starts ntpd. This allow the ntpd daemon to be pretty close to a 0 offest and distance.


If you have the "set date & Time Automatically" checked it should be in staratum 3 (or 4) but not 16. 16 means it can't connect to the ntp server (the default one is time.apple.com) and this is usually a firewall issue. I changed mine to something else and I since have no more sync issue.

As I deal with ntp server  for work it was easier to figure out the issue but I will agree with you that sometimes for now reason the ntpd version that apple provide can't connect (and sync) to the net server set int /etc/ntp.conf


Regards, Rodolphe


--


|        Rodolphe Pineau    RTI-Zone        |

|         http://www.rti-zone.org/          |

|   Robotics / Unix / Mac OS X / Astronomy  |