Steve and Stéphane, the decision is of course up to you since you know how notify-reboot-required is supposed to be used. I'll just provide some background information.
1. When resolvconf is installed it may be missing nameserver information. I am not talking about the #923685 problem here (which persists after reboot), just about the problem, e.g., that dhclient has already obtained a nameserver address A at the time resolvconf is installed and has inserted A into /etc/resolv.conf. Although the resolvconf package has a mechanism for telling other packages to provide nameserver information after it's installed, to date only one package (dnsmasq) uses this mechanism. Now, resolvconf includes the pre- installation resolv.conf in its database until the first reboot, so A doesn't get lost. But if the dhclient-configured interface is brought down then A is not removed from the database; so the resolver will try that address even though it's no longer available. This malfunction goes away after the first reboot. 2. When resolvconf is removed it leaves a static file behind at /etc/resolv.conf. Again, if this file contains A then A won't be removed if the associated interface is deconfigured. Consider the case where A is "127.0.0.1" associated with a caching nameserver which resolvconf supplied with non-loopback nameserver addresses before it was removed. If the caching nameserver is stopped then all nameserver addresses will be lost. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929404 Title: resolvconf package should notify reboot required on installation and removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/929404/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
