Steve Kostecke <[EMAIL PROTECTED]> writes: >On 2008-09-11, Bill Unruh <[EMAIL PROTECTED]> wrote:
>> A question has arisen in another group-- What happens if, when ntp starts >> up, the remoter server is unavailable ( eg no DNS or no connection)? >> This is highly likely to be the case for a laptop for example, where the >> connection with the local network is only brought up by the user after a >> while, or on wakeup from a power outage when the net may be unstable or the >> router be out when ntp comes up. >As of 4.2.4p5 ntpd does the right thing in these situations. Here's an >extract from the stable release ChangeLog: >(4.2.4p5) 2008/08/17 Released by Harlan Stenn <[EMAIL PROTECTED]> >* [Bug 841] Obsolete the "dynamic" keyword and make deferred > binding to local interfaces the default. > Emit a warning if that keyword is used for configuration. "deferred binding to local interfaces" means what? If my server is a pool.ntp server, but my gateway is down when I boot up, will it eventually bind to pool? Or just say-- the hell with it? What counts as "local"? Did the dynamic keyword ever work? The web docs say that it is not yet implimented. >The complete ChangeLog is at http://archive.ntp.org/ntp4/ChangeLog-stable >-- >Steve Kostecke <[EMAIL PROTECTED]> >NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
