powernowd does not start cleanly on Jaunty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
powernowd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Two problems with script /etc/init.
- it tries to use /sbin/lsmod
- it prints a "Usage:" message on standard output
The first problem affects other packages: it is tracked on bug #340666
The second problem was first reported on bug #340300, now marked as duplicate.
These problems can be reproduced as follows.
root@jaunty:
/etc/init.
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
That is not the only error message from the script, as can be seen from Bug 340300 (interesting that both were reported back to back).
The attached patch eliminates the error messages, but that may be hiding something that needs to be fixed.