Red Hat Bugzilla – Bug 498119
xinetd init script 'status' does not set return value
Last modified: 2015-03-04 18:56:39 EST
Created attachment 341672 [details]
Patch fixes init script status retval
The xinetd init script does not set its return value correctly when invoked with 'status'. For example, if xinetd is stopped, the return value is 0:
# service xinetd status
xinetd is stopped
# echo $?
The proper return value in this case is 3. For expected behavior, see . The attached patch fixes the issue.
This appears to be identical to #232887 which was filed against Fedora Core 6 and has been fixed for ages in the Fedora packages (the fix is the same as yours, Ian). Any reason this rather trivial fix hasn't made it into either RHEL 5.4 or 5.5?
I guess it's because there was no extra pressure from customers to get it there. Contacting our support and requesting this fix could help. Otherwise I can't guarantee this will be fixed in RHEL-5.
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.