[ntp:questions] Consider the Undisciplined Local Clock synchronized at start-up
devnull at localhost.com
Fri Mar 30 16:42:07 UTC 2007
Steve Kostecke wrote:
> Spoon wrote:
>> I've configured one box to serve its local clock to another box.
>> (I want them to drift together.)
>> When I start the "server" daemon, it takes a while (three minutes)
>> for the local clock to be considered "synchronized".
> This is normal.
I don't know what "normal" means in this context.
By definition, the undisciplined local clock is synchronized. Therefore,
one might expect that ntpd would consider it as such. Am I on drugs?
>> Thus, if I start the server and client together, the sender will refuse
>> to reply to the client's iburst. (Please correct any misconception.)
> The server will reply immediately that it is at Stratum 16. At that
> point you've "used up" the initial burst.
>> Is it possible to tell the server to consider his clock synchronized
>> as soon as the daemon starts?
More information about the questions