Suppose resolvconf were to be changed so that it omitted information
from resolv.conf that appeared to be associated with a "down" interface.
What if a resolvconf update happens when some interface happens
temporarily to be down? Information gets omitted even though it should
not be. What if a pa
someone has to do a check, because there are times that the cleanup will
not happen. if vpnc gets a kill -9, it can't cleanup and it would be
difficult to argue that that is a bug with vpnc.
there is a convention as you mention. if resolveconf enforced it, others
would follow it. for that matter t
One question is whether or not it is resolvconf's responsibility to
check upness of interfaces. Resolvconf is really just a registry.
Suppliers of nameserver information are responsible for updating the
information they have supplied. So the bug in this case is certainly
vpnc's.
Given that the b
is there anyway to inspire action on this bug? it is still happening and
it is super annoying!
--
resolvconf should not use dns info for interfaces that are down
https://bugs.launchpad.net/bugs/262650
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Just seen this too. Also using vpnc - presumably it did not terminate
correctly last time I shut down.
--
resolvconf should not use dns info for interfaces that are down
https://bugs.launchpad.net/bugs/262650
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Ubuntu 8.10
resolvconf 1.42ubuntu2
network-manager 0.7~~svn20081018t105859-0ubuntu1
network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1
I'm experiencing exactly the same as described in #51339, i.e. my
/etc/resolv.conf looks like this:
# Dynamic resolv.conf(5) file for glibc resolver(3) gene
Benjamin's patch isn't in resolvconf trunk, I applied it locally and
tested it with: vpnc + resolvconf + dnsmasq.
The patch now has an ugly workaround to work with dnsmasq also and works
with more interfaces.
Although I think it would be better not to have vpnc die in the first
place, so its reso
** Attachment added: "Only return interfaces that are up"
http://launchpadlibrarian.net/17156898/list-records.patch
--
resolvconf should not use dns info for interfaces that are down
https://bugs.launchpad.net/bugs/262650
You received this bug notification because you are a member of Ubuntu
B
