Bug 238026 - Wrong init script
Wrong init script
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: exim (Show other bugs)
5.0
All Linux
low Severity low
: ---
: ---
Assigned To: Miroslav Lichvar
:
Depends On:
Blocks: 237789 238027 238028
  Show dependency treegraph
 
Reported: 2007-04-26 11:58 EDT by Michal Marciniszyn
Modified: 2014-02-10 18:02 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-12-02 07:15:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Marciniszyn 2007-04-26 11:58:10 EDT
Description of problem:
The exim init script may end with error code 0 even when the service is not
started/running. Also there is minor bug with wrong return code of unimplemented
feature of the script (1 instead of 3).

Version-Release number of selected component (if applicable):
all

How reproducible:
always

Steps to Reproduce:
1. service network stop
2. service exim start/status
3. echo $?
  
Actual results:
0

Expected results:
non-zero error code/status of the service

Additional info:
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:
http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html
http://intranet.corp.redhat.com/ic/intranet/InitscriptGuidelines.html

For an example of the script that returns the error codes correctly and always
runs status see:
http://devserv.devel.redhat.com/~mmarcini/amd

This bug is tracked by 237789.
Comment 7 errata-xmlrpc 2009-12-02 07:15:13 EST
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.

http://rhn.redhat.com/errata/RHBA-2009-1627.html

Note You need to log in before you can comment on or make changes to this bug.