On 2009-07-01 08:38:22 +0200, Kurt Roeckx wrote: > On Tue, Jun 30, 2009 at 10:25:59PM +0200, Vincent Lefevre wrote: > > On 2009-06-30 20:55:00 +0200, Kurt Roeckx wrote: > > > I think your problem is that you have a local named that returns > > > a permanent error to ntpd when it tries to resolv. > > > > Yes, because at boot time, the machine isn't connected yet. > > So why do you need to run named localy?
Because my router doesn't handle IPv6 and makes programs freeze. I also had to install it on another machine, but I don't remember what problem it solved actually (probably for caching, but I'm not sure). > > But in that case, why isn't there a script in /etc/network/if-up.d > > to restart ntpd? In fact there was one in the past, but it has been > > removed probably because: > > > > ntp (1:4.2.4p0+dfsg-1) unstable; urgency=low > > > > This version of ntp will periodically rescan the network interfaces to > > pick up new and deleted interfaces. This should supplant most or all > > of the various workarounds in use such as restarting the daemon in > > /etc/network/if-up.d/ or /etc/ppp/ip-up.d/. > > > > -- Peter Eisentraut <[email protected]> Thu, 3 May 2007 11:32:29 +0200 > > > > So, ntpd doesn't behave as documented. > > As far as I know, it does behave as documented. The rescanning of > the interface is to pick up new IP addresses of the interfaces. > It will not try to resolve the names of the ntp servers/peers > again. Then the script in /etc/network/if-up.d should be re-added. -- Vincent Lefèvre <[email protected]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
