On Thursday, 16 November 2006, you (Simon Kelley) wrote: [...cut...] > No, it checks the mtime of resolv.conf each time it does a DNS query, > provided more than one second has elapsed since the last check.
Looks like it doesn't. It again happened just a few minutes ago: - resolvconf has triggered update scripts including dnsmasq's, so that /var/run/dnsmasq/resolv.conf was changed at 07:53:41 - ddclient made a DNS request at 07:53:41, a few milliseconds after dnsmasq update, and fails. - dnsmasq rereads its resolv.conf at 07:57:55, more than 4 minutes later. Of course I assume resolvconf runs the scripts in up-up.d sequentially and in listing order (as with run-parts). Here's my listing: $ ls -l /etc/ppp/ip-up.d total 36 -rwxr-xr-x 1 root root 891 Jul 12 16:34 0000usepeerdns -rwxr-xr-x 1 root root 467 Dec 13 2005 000resolvconf -rwxr-xr-x 1 root root 203 Nov 4 18:57 0clampmss -rwxr-xr-x 1 root root 237 Jun 14 06:55 0firewall -rwxr-xr-x 1 root root 353 Oct 16 13:29 1polipo -rwxr-xr-x 1 root root 1677 Jan 14 2006 clamav-freshclam-ifupdown -rwxr-xr-x 1 root root 814 Apr 15 2006 ddclient -rwxr-xr-x 1 root root 295 Aug 14 2005 exim4 -rwxr-xr-x 1 root root 391 Sep 24 22:11 fetchmail [...cut...] > My hunch is that this is a ppp/resolv.conf bug, and not a dnsmasq one. > It certainly necessary to understand exactly what sequence of events is > happening here to fix it. That's what for I added the pppd log. With a minimum of deductions we can infer execution order of interesting parts (we should first assume that other software is ok, otherwise we have no chance to solve anything). -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
