Bug 509754
| Summary: | -n ${GOVERNOR} typo in /etc/init.d/cpuspeed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Maciej Żenczykowski <zenczykowski> |
| Component: | cpuspeed | Assignee: | Jarod Wilson <jarod> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | jarod |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-06 13:51:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
cpuspeed-1.5-10.fc11 was pushed to the updates repo last Wednesday. *** This bug has been marked as a duplicate of bug 505837 *** # yum list extras Loaded plugins: dellsysidplugin2, refresh-packagekit Extra Packages cpuspeed.x86_64 1:1.5-10.fc11 installed ... So it doesn't seem to be live yet (I installed manually from koji). You have stale repo data or something. $ yum list cpuspeed Loaded plugins: refresh-packagekit Installed Packages cpuspeed.x86_64 1:1.5-9.fc11 @updates Available Packages cpuspeed.x86_64 1:1.5-10.fc11 updates Yeah, it does seem that "rm -rf /var/cache/yum/*" has revealed a whole bunch of updates. Sorry, for the bother. |
My box has an EIST capable cpu, but missing ACPI tables, hence frequency scaling doesn't work. In /etc/init.d/cpuspeed the line: if [ -d ${cpu0freqd} -a -n ${GOVERNOR} ]; then should be: if [ -d ${cpu0freqd} -a -n "${GOVERNOR}" ]; then to prevent errors about ] misparsing when GOVERNOR is empty. # rpm -q --whatprovides /etc/init.d/cpuspeed cpuspeed-1.5-8.fc11.x86_64 However, I believe this has actually been fixed in a non-pushed to updates version of cpuspeed. At least: # rpm -q --whatprovides /etc/init.d/cpuspeed cpuspeed-1.5-10.fc11.x86_64 doesn't seem to have this issue.