*** This bug is a duplicate of bug 97513 ***
https://bugs.launchpad.net/bugs/97513
I have confirmed this; squid is controlled using upstart so actually
starts up after the NetworkManager has bought up the network interface
as it depends on this event (which puts us in a slightly
different/better position to the issue described in Fedora)
However, when the network configuration changes, squid does not restart
and pickup any new resolv.conf configuration. This would impact on
people using VPN (as above) or hopping between network locations which
generate different resolv.conf configurations.
--
Squid requires restart after Network Manager made connection to network
https://bugs.launchpad.net/bugs/659958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
