> Perhaps what is happening is: dnsmasq is running /sbin/resolvconf before > the resolvconf package's postinst has set up needed directories and > symlinks. /sbin/resolvconf thus aborts (with the error message) when it > sees that the needed directory is missing.
That is consistent with what I see from apt-get install messages. Dnsmasq is set up before resolvconf. The /etc/resolv.conf file remains in its original state (the manually set nameserver) until reboot (or /etc/init.d/dnsmasq restart if you don't care to do a full reboot). > Submitter: Did you observe this (omission of 127.0.0.1 from the > nameserver list in /etc/resolv.conf until the first reboot)? Yes. After reboot (or dnsmasq restart) I get 127.0.0.1 as the nameserver. I note also that installing dnsmasq first, then installing resolvconf next gives equivalent behaviour. That is, dnsmasq needs a restart after resolvconf is installed, which then installs 127.0.0.1 (Installing resolvconf first, then dnsmasq afterwards does not require a restart from dnsmasq since dnsmasq sets itself up in this case after resolvconf is properly set up. So the nameserver setting becomes 127.0.0.1 with no explicity restart needed.) > Assuming that the above diagnosis is correct, possible cures are: [snip possibilities] > - Hard to do this consistently with the need to respect > administrator customizations. Yes. Forcing a reboot after installation (which is what I was doing as part of my install procedure) solves it too, but every time you do that, a techie cries. regards PJ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org