Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 237805

Summary:	Wrong init script
Product:	Red Hat Enterprise Linux 5	Reporter:	Michal Marciniszyn <mmarcini>
Component:	quagga	Assignee:	Martin Bacovsky <mbacovsk>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5.0	CC:	tvujec
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-06-21 13:06:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	237789, 237808, 237809

Description Michal Marciniszyn 2007-04-25 14:59:26 UTC

Description of problem:
If the /etc/quagga/bgpd.conf does not exist or the networking is shut down, then
the script always ends with error code 0 (even if status is invoked). There are
also wrong return codes in the script.

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

How reproducible:
always

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

Expected results:
non-zero exit code due to our guidelines or 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 1 Martin Bacovsky 2007-06-21 13:06:30 UTC


*** This bug has been marked as a duplicate of 243143 ***

Comment 2 Martin Bacovsky 2007-06-22 13:36:39 UTC

The inistcript is wrong but just FYI:
service network stop doesn't affect value of NETWORKING variable in
/etc/sysconfing/network so [ "${NETWORKING}" = "no" ] && exit 1 can pass even
with  network down.