Bdale wrote: > 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.
This is doable and quite performant at least under Linux via rtnetlink(7) messages. In other systems there might be sth. similiar and you can enumerate all interfaces and addresses every N seconds in the main select/poll loop. and watch for changes there. If sth. changed just try to (re)connect all configured time servers and ask for the time. > So, there is a balance, and if we're going to implement a behavior like > this it probably needs to be made optional somehow. This solution works at least. The current one is just useless, since you cannot contact ANY server until networking is up. Debian scripts start networking just AFTER any script in /etc/rcS.d/ The proposed solution of using /etc/networking/if-up.d/ works without any problem for most of your users. Actually unbuntu "Dapper Drake" is just doing it this way and I never had any problems. We fixed it for our customers the same way. But I agree, that there should be an option to turn this off. Actually there are many already. Some as simple as "rm -f /etc/networking/if-up.d/ntpdate" should be enough for those advanced admins. Please remember that /etc/networking/if-up.d/ntpdate runs, when the ADMIN starts the networking and not on every link up/down. Regards Ingo Oeser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
