[ntp:questions] NTP on small 100% Linux LAN : reasonable access control policy ?

Richard B. Gilbert rgilbert88 at comcast.net
Sun Aug 1 18:07:41 UTC 2010

David J Taylor wrote:
> "Richard B. Gilbert" <rgilbert88 at comcast.net> wrote in message 
> news:ioednXH_-ZfyMsjRnZ2dnUVZ_hSdnZ2d at giganews.com...
> []
>> Be prepared to wait as long as ten or twelve hours to get really close 
>> synchronization.  NTP was never intended for systems running only 
>> eight hours a day.  You can be "close" in thirty minutes or less but 
>> it takes many hours to get both close and stable.  It also helps to 
>> run your server in a controlled environment; temperature changes will 
>> affect your clock.
> If "close" is within a few tens of milliseconds, NTP can be there very 
> quickly with the appropriate servers and settings.
> Cheers,
> David

If your definition of "close" is used, you hardly need NTP.  My PC 
running Windows/XP SP3 is within a few milliseconds running nothing more 
than W32TIME.

I've had a Sun Ultra 10 Workstation running Solaris keep time within 
fifty microseconds or better using a GPS timing receiver and NTPD.

More information about the questions mailing list