On Wed, 2005-03-30 at 16:18 -0400, Tony Rowe wrote: > I should be clear about this. This was a > trial. I did an apt-get install resolvconf. Then I mv'ed my > manually-created /etc/resolv.conf out of the way.
Resolvconf is met to work with /etc/resolv.conf a symlink pointing to /etc/resolvconf/run/resolv.conf, the dynamically generated configuration file. If resolvconf is installed then programs like pppconfig refrain from writing to /etc/resolv.conf directly. Therefore I find it hard to understand why installing resolvconf and deleting /etc/resolv.conf actually resulted in /etc/resolv.conf getting updated by 0dns-up. However, I don't know pppconfig that well. I use ifupdown to control ppp interfaces. Tony Rowe wrote: > Which program owns resolv.conf (the man page for resolv.conf does > exist on a fresh install - I checked)? If no program owns it (it is > non-obvious to me which program owns it), what is policy on who can > create (touch) a resolv.conf? No package owns it and there is no formal policy governing its use. However, the maintainers of the packages that affect resolv.conf do work together to ensure that things work properly. You seem to have found circumstances in which the right thing is not being done. As it isn't a resolvconf problem I probably won't have more to say about this issue. -- Thomas Hood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]