Description of problem:
Through the script, following constructions are used:
[ -f /sbin/capiinit ] || exit 0
[ -f /etc/capi.conf ] || exit 0
Effectively, they return 0 even when the service is not started or running
(start/status command). Also wrong return codes are present through the script.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. remove capi.conf file
2. service capi start/status
3. echo $?
non-zero error code/correct service status
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.
Proposing for RHEL-5.3, waiting with final ACK on developer review.
Read ya, Phil
*** Bug 242481 has been marked as a duplicate of this bug. ***
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.