powernowd now generating error messages under Jaunty

Bug #340300 reported by Noel J. Bergman
2
Affects Status Importance Assigned to Milestone
powernowd (Ubuntu)
New
Undecided
Unassigned

Bug Description

The error can be reproduced as follows:

# /etc/init.d/powernowd.early
 * Usage: /etc/init.d/powernowd {start|stop|restart|force-reload}
root@jaunty:/var/log# /etc/init.d/powernowd.early start
/etc/init.d/powernowd: 180: /sbin/lsmod: not found
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> ...]

Revision history for this message
Andreas Moog (ampelbein) wrote :

Thanks for your report. I duplicated it to bug #340301 which describes a similar issue.

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.