Red Hat Bugzilla – Bug 237940
cpuspeed init script uses some incorrect exit codes
Last modified: 2014-02-10 18:02:12 EST
Description of problem:
Following code ends the script with error code 0 when the binary does not exist
even though the service was not started.
[ -f /usr/sbin/cpuspeed ] || exit 0
There are also minor errors in wrong error codes (unimplemented feature
(reload/start_again or something) has error code 3 and not one.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rename the binary
2. service cpuspeed start/status
3. echo $?
correct error code/status of the service
When fixing this bug, please obbey our init script guidelines and be sure that
status command is run correctly.
Our guidelines are on following two pages:
For an example of the script that returns the error codes correctly and always
runs status see:
This bug is tracked by 237789.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Fix is in cpuspeed 1.2.1-1.46.el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.