Squid requires restart after Network Manager made connection to network
Bug #659958 reported by
Tobias Krais
This bug report is a duplicate of:
Bug #97513: Squid requires restart after Network Manager made connection to network.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid (Fedora) |
Unknown
|
Unknown
|
|||
squid (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: squid
After Network Manager made connection to a network (e.g. a VPN network) I have to restart my squid. I found the same bug in Fedora project:
https:/
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: squid 2.7.STABLE7-
ProcVersionSign
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Oct 13 16:35:02 2010
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: squid
To post a comment you must log in.
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.