irqbalance enabled unconditionally, can't be disabled via debconf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
irqbalance (Debian) |
Fix Released
|
Unknown
|
|||
irqbalance (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Maverick |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: irqbalance
[using 0.55+20091017-
irqbalance gets enabled unconditionally upon installation. The user's answer to the question whether it should be enabled (upon installation or dpkg-reconfigure) gets ignored:
,---
| $ cat /etc/default/
| #Configuration for the irqbalance daemon
|
| #Should irqbalance be enabled?
| ENABLED=1
| #Balance the IRQs only once?
| ONESHOT="0"
| $ sudo dpkg-reconfigure -ftext irqbalance
| stop: Unknown instance:
| Configuring irqbalance
| -------
|
| Enable the irqbalance daemon to balance IRQs on SMP systems and systems with
| hyperthreading.
|
| Would you like to enable irqbalance? n
|
|
| irqbalance can run in one shot mode, where the IRQs are balanced only once. This
| is advantageous on hyperthreading systems such as the Pentium 4, which appear to
| be SMP systems, but are really one physical CPU.
|
| Would you like to balance the IRQs once? y
|
|
| irqbalance start/running, process 1496
| $ cat /etc/default/
| #Configuration for the irqbalance daemon
|
| #Should irqbalance be enabled?
| ENABLED=1
| #Balance the IRQs only once?
| ONESHOT="1"
`---
=> dpkg-reconfigure managed to change the ONESHOT setting but not the ENABLED setting.
The problem is caused by a confusion over where to use "ENABLED" and where "ENABLE". I'm attaching a trivial patch which fixes the problem.
Changed in irqbalance (Debian): | |
status: | Unknown → New |
tags: | added: patch-forwarded-debian |
tags: | added: lucid maverick patch |
tags: | added: server-mrs |
Changed in irqbalance (Debian): | |
status: | New → Fix Released |
Thanks this will be fixed in maverick.
chuck