squid-deb-proxy will not be started on transition from runlevel 1 to 2
Bug #820697 reported by
Clint Byrum
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/
foo/etc/
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
Related branches
lp:~racb/squid-deb-proxy/upstart-runlevel-start
- squid-deb-proxy-developers: Pending requested
-
Diff: 12 lines (+1/-1)1 file modifieddebian/squid-deb-proxy.upstart (+1/-1)
Changed in squid-deb-proxy (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
status: | Triaged → Won't Fix |
Changed in squid-deb-proxy (Ubuntu Trusty): | |
assignee: | nobody → Robie Basak (racb) |
To post a comment you must log in.
Bug 831628 suggests to me that the start condition should match the current squid3 start condition: just "start on runlevel [2345]".