On Thu, Sep 11, 2008 at 12:21:29PM +0200, Henning Brauer wrote: > * Henning Brauer <[EMAIL PROTECTED]> [2008-09-10 10:39]: > > ntpd -s will time out eventually, but the 'eventually' might be > > painfully far away. it's the dns routines that block and cause these > > problems. i know how to fix this but haven't found the time to do so > > yet. maybe i get a chance on the flight later today. maybe. > > didn't find too much time on the flight, but finished this morning. > > basically, move dns to its own process. the parent process is just not > allowed to block no matter what. the dns process can drop privs but > not chroot. > Hello, It's very nice, now it takes around ~20 secs or so to timeout in the following scenarios: * if hostname in ntpd.conf doesn't resolve * if wireless interface isn't associated
Thanks
