upstart jobs result in dead squid-deb-proxy and/or squid-deb-proxy-avahi
Bug #677276 reported by
Clint Byrum
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| squid-deb-proxy (Ubuntu) |
Fix Released
|
Undecided
|
Clint Byrum | ||
Bug Description
Binary package hint: squid-deb-proxy
The way the upstart jobs are arranged causes squid-deb-proxy to not start if there is no valid internet connection on startup, for instance if a wifi connection is in use.
Also, because squid-deb-
These issues were uncovered and discussed some while verifying this bug:
https:/
Related branches
lp:~clint-fewbar/ubuntu/natty/squid-deb-proxy/fix-upstart-jobs
- Bilal Akhtar (community): Approve
- Ubuntu branches: Pending requested
-
Diff: 52 lines (+13/-4)3 files modifieddebian/changelog (+9/-0)
debian/squid-deb-proxy.squid-deb-proxy-avahi.upstart (+2/-2)
debian/squid-deb-proxy.upstart (+2/-2)
| Changed in squid-deb-proxy (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Clint Byrum (clint-fewbar) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in squid-deb-proxy (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package squid-deb-proxy - 0.3.3
---------------
squid-deb-proxy (0.3.3) natty; urgency=low
* Adjusting upstart job so restarting squid-deb-proxy does not result
in killing squid-deb-
* Also adjusting upstart job so squid-deb-proxy does not get started
a real network interface is up and all local filesystems are mounted
-- Clint Byrum <email address hidden> Thu, 18 Nov 2010 16:27:24 -0800