On Mon, 2006-02-27 at 08:25 +0100, Vincent Lönngren wrote: > Package: ntp > Version: 1:4.2.0a+stable-8.1 > Followup-For: Bug #289267 > > If ntpd was restarted when an interface is added, it would avoid > problems with ntpd starting when there are no hosts available.
The problem with this plan is that the NTP protocol takes a while to "settle" its estimation of the correct time, and restarting the daemon every time an interface is added could cause hosts with one or more particularly dynamic interfaces to never achieve good time sync. It would be nice if ntpd could be poked somehow to go notice changes in the list of available interfaces and/or server/peer information without having to start over from scratch as happens with a full restart, but I don't know offhand if that's possible with the current code? Perhaps someone can investigate this. So, there is a balance, and if we're going to implement a behavior like this it probably needs to be made optional somehow. Bdale
