upstart jobs result in dead squid-deb-proxy and/or squid-deb-proxy-avahi

Bug #677276 reported by Clint Byrum on 2010-11-19
This bug affects 2 people
Affects Status Importance Assigned to Milestone
squid-deb-proxy (Ubuntu)
Clint Byrum
Nominated for Lucid by Clint Byrum
Nominated for Maverick by 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-proxy-avahi is marked as 'stop on stopping squid-deb-proxy', restarting squid-deb-proxy results in squid-deb-proxy-avahi being stopped but never started again.

These issues were uncovered and discussed some while verifying this bug:

Related branches

Changed in squid-deb-proxy (Ubuntu):
status: New → In Progress
assignee: nobody → Clint Byrum (clint-fewbar)
Launchpad Janitor (janitor) wrote :

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-proxy-avahi. (LP: #677276)
  * 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

Changed in squid-deb-proxy (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers