Bug 204132 - cpuspeed startup scrips fails in unduly noisy manner
Summary: cpuspeed startup scrips fails in unduly noisy manner
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: cpuspeed
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jarod Wilson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-25 19:14 UTC by Michal Jaegermann
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-08 15:14:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
fix for a cpuspeed startup script (782 bytes, patch)
2006-08-25 19:14 UTC, Michal Jaegermann
no flags Details | Diff

Description Michal Jaegermann 2006-08-25 19:14:28 UTC
Created attachment 134954 [details]
fix for a cpuspeed startup script

Comment 1 Michal Jaegermann 2006-08-25 19:14:28 UTC
Description of problem:

/etc/init.d/cpuspeed is turned on by default but it may fail.
At least on a start it checks for that condition but only after
it produced a message which is not really relevant in the context
(cf. bug 201463 which, in a sense, may be not a bug at all).

'service cpuspeed stop' may just fail by trying to read from a
non-existent location and here a relevant check is just missing.

Sure, one can always do 'chkconfig cpuspeed off' but maybe problems
are only temporary specific to some kernels?

Attached is a proposed patch to deal with the problem.

Version-Release number of selected component (if applicable):
cpuspeed-1.2.1-1.40.fc6

How reproducible:
always on a machine where cpuspeed does not work

Comment 2 Jarod Wilson 2007-01-08 15:14:35 UTC
Eep, finally got mass-reassigned all the cpuspeed bugs over the weekend... I
believe this one is taken care of in the latest rawhide build. I like the
null-redirect on modprobing acpi-cpufreq, but not for $DRIVER. Since the user
must manually specify $DRIVER, I like spitting an error if they screwed up.


Note You need to log in before you can comment on or make changes to this bug.