View Single Post
Old 21st August 2009
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Default

Note, as has been mentioned, the ntp daemon will NOT start serving time UNLESS and UNTIL it is sync's AND the DRIFT PRECISION (aka. CLOCK DISCIPLINE) self-adjusts to some very tight tolerance (stability).

http://www.openbsd.org/faq/faq6.html#OpenNTPD, reads, in part,

Quote:
When you have ntpd(8) listening, it may happen that other machines still can't synchronize to it! A freshly started ntpd(8) daemon (for example, if you just restarted it after modifying ntpd.conf) refuses to serve time information to other clients until it adjusts its own clock to a reasonable level of stability first. When ntpd(8) considers its own time information stable, it announces it by a "clock now synced" message in /var/log/daemon. Even if the system clock is pretty accurate in the beginning, it can take up to 10 minutes to get in sync, and hours or days if the clock is not accurately set at the start.
More info on the openNTP implementation in the openBSD distro at, http://www.advogato.org/person/dtuck....html?start=52.

/S
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.
Reply With Quote