I don't think is a correct fix; NetworkManager should *not* overwrite
the file pointed to by the /etc/resolv.conf symlink.
I've got two systems here running Kubuntu Karmic Koala, with
NetworkManager (and kdenetworkmanager), dhclient, dnsmasq, resolvconf
and openvpn installed. If boot in single
In the case I outlined, the only way I could catch it happening was to
shut down and then boot the system off of a Live USB installation, so I
could mount the root filesystem and inspect it before NetworkManager was
started up again (using the GRUB 'recovery console' and 'drop to a root
shell'
I've been running with a patched version of nm-named-manager for a few
months now; the patch just removes the ability for network-manager to
directly write to /etc/resolv.conf completely, and it's been completely
stable. Every single time I start up, resolvconf is still in use as
expected.
--
Ditto to #18; that solution worked for me (for both shorewall and
shorewall6).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
shorewall does not start at boot
To manage notifications
