Bug 243711 - Wrong init script
Summary: Wrong init script
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rwho
Version: 5.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Honza Horak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 243710
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-11 14:27 UTC by Michal Marciniszyn
Modified: 2014-02-10 23:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-13 17:33:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch for rwhod.init to be same as RHEL-6 (2.47 KB, patch)
2011-07-21 15:48 UTC, Honza Horak
no flags Details | Diff

Description Michal Marciniszyn 2007-06-11 14:27:13 UTC
+++ This bug was initially created as a clone of Bug #243710 +++

Description of problem:
The rwhod init script return incorrect error codes and following construction
may prevent the correct status command call:
if [ ${NETWORKING} = "no" ] ; then
        exit 0
fi

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

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


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 1 Ondrej Vasik 2011-02-22 09:07:50 UTC
As 4.9 is the last maintainance release of RHEL-4. This problem was fixed in RHEL-6 , in RHEL-5 it still exists, but the report https://bugzilla.redhat.com/show_bug.cgi?id=243710 was closed DEFERRED by pm bot. So moving that one report to RHEL-5 (as we probably could fix the initscript in some fastrack.

Comment 10 Honza Horak 2013-03-13 17:33:24 UTC
This bug has been fixed in RHEL-6 and there is no chance to fix this in RHEL-5 any more, since RHEL 5.10 is going to include only serious fixes.


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