Red Hat Bugzilla – Bug 237752
Wrong init script
Last modified: 2014-02-10 18:01:46 EST
Description of problem:
This construction returns error code 0 even when the service is not correctly
[ -x /usr/sbin/acpid ] || exit 0
[ -f /proc/acpi/event ] || exit 0
Also the status command (that should always return state of the service) is
ended withou even finding out the state.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rename conf file/change permissions on binary
2. service acpid start
3. echo $?
correct error code
When fixing this bug, please obbey our init script guidelines and be sure that
status command is implemented correctly.
Our guidelines are on following two pages:
So what would you suggest how to fix it? We can't really run the initscript
without kernel support. And letting it always fail with an error if the kernel
doesn't support ACPI isn't really good either.
Read ya, Phil
Init script is fixed in devel.
*** Bug 232153 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. This request will
be reviewed for a future Red Hat Enterprise Linux release.
Unless this moves to 5.4 by Tuesday, the bugbot is going to automatically close
it. Please either either get dev and qa acks for FastTrack or move to 5.4 before
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 therefore 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.