Squid requires restart after Network Manager made connection to network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid (Debian) |
Fix Released
|
Unknown
|
|||
squid (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
squid3 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: squid
Squid uses its own resolver, getting a list of name servers on startup from /etc/resolv.conf. On a roaming laptop, this information is missing until a network connection is made, which happens after squid is launched and has loaded an empty /etc/resolv.conf.
This is a bug because on a roaming laptop, squid does not "just work."
The net effect is that squid will not work on a roaming laptop until:
* squid is restarted after a network connection has been established, or
* the user is sophisticated enough to put the dns_nameservers tag into /etc/squid/
A proposed solution would be to make squid dependent upon a network connection being up, so that squid starts after a network becomes available and stops when the network goes away. One possible downside to this approach is that squid, when asked to shut down, might think some network connections are open, and the default action is to wait 30 seconds before actually shutting down, set through the shutdown_lifetime tag. The default squid.conf might need to be modified so that squid shuts down immediately when a network connection is shut down.
After all, there is no need for squid if there is no network connection, is there?
Marty
Changed in squid: | |
status: | Incomplete → Confirmed |
Changed in squid3 (Ubuntu): | |
status: | New → Confirmed |
tags: | added: patch |
Changed in squid (Debian): | |
status: | Unknown → New |
Changed in squid (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in squid (Debian): | |
status: | New → Fix Released |
So basically start squid when you bring up your network right?
Thanks
chuck