Bug 237809

Summary:	Wrong init script
Product:	[Fedora] Fedora	Reporter:	Michal Marciniszyn <mmarcini>
Component:	quagga	Assignee:	Martin Bacovsky <mbacovsk>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	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-07-26 13:32:35 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:	237805
Bug Blocks:

Description Michal Marciniszyn 2007-04-25 15:02:34 UTC

+++ This bug was initially created as a clone of Bug #237805 +++

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-07-26 13:32:35 UTC


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