squid-deb-proxy will not be started on transition from runlevel 1 to 2

Bug #820697 reported by Clint Byrum
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
squid-deb-proxy (Ubuntu)
Won't Fix
Low
Unassigned
Trusty
Triaged
Low
Unassigned

Bug Description

foo/etc/init/squid-deb-proxy.conf:start on (local-filesystems and net-device-up IFACE!=lo)
foo/etc/init/squid-deb-proxy.conf:stop on runlevel [!2345]

local-filesystems and net-device-up will not necessarily be emitted on transition from runlevel 1 to 2. The squid.conf file was patched to fix this bug recently as well in bug 561779

Tags: runlevel1

Related branches

James Page (james-page)
Changed in squid-deb-proxy (Ubuntu):
status: New → Triaged
importance: Undecided → Low
status: Triaged → Won't Fix
Revision history for this message
Robie Basak (racb) wrote :

Bug 831628 suggests to me that the start condition should match the current squid3 start condition: just "start on runlevel [2345]".

Robie Basak (racb)
Changed in squid-deb-proxy (Ubuntu Trusty):
assignee: nobody → Robie Basak (racb)
Revision history for this message
Robie Basak (racb) wrote :

I didn't realise until I went to do this that the package is synced from Debian, is a native package, and uses upstream bzr in lp:squid-deb-proxy. So I've submitted an MP, and would like feedback from mvo on whether it's worth an Ubuntu delta here or not, or if he can just upload a fix to Debian and sync (doesn't look like recent changes in Debian would be blocked by FF to me).

Changed in squid-deb-proxy (Ubuntu Trusty):
assignee: Robie Basak (racb) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.