squid is not started on runlevel transition 1 -> 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid (Ubuntu) |
Fix Released
|
Medium
|
Clint Byrum | ||
Lucid |
Fix Released
|
Medium
|
Unassigned | ||
Maverick |
Fix Released
|
Medium
|
Unassigned | ||
Natty |
Fix Released
|
Medium
|
Clint Byrum |
Bug Description
Binary package hint: squid
when you go to runlevel 1 for maintenance with 'telinit 1', squid is stopped correctly
when you go back to runlevel 2 with 'telinit 2' squid is not started
because /etc/init/
in karmic, squid would stop on entering runlevel 1 and be started again on entering runlevel 2
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: squid 2.7.STABLE7-
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelMo
Architecture: i386
Date: Mon Apr 12 21:48:49 2010
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: squid
Changed in squid (Ubuntu): | |
importance: | Undecided → Low |
Changed in squid (Ubuntu Maverick): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in squid (Ubuntu Lucid): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in squid (Ubuntu Natty): | |
assignee: | nobody → Clint Byrum (clint-fewbar) |
status: | Triaged → In Progress |
tags: |
added: verification-done removed: verification-needed |
Is it low importance? It's easily worked around if I know it occurs, but if I don't know this bug exists then I'm left with a server at runlevel 2 without squid, and it may cause users all kinds of problems before they get back to me and I work out what's wrong.