Bug 161209

Summary:	xined status always returns 0
Product:	[Fedora] Fedora	Reporter:	paul <paul.miles>
Component:	xinetd	Assignee:	Jan Safranek <jsafrane>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	mattdm
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:	xinetd-2.3.14-9.fc6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-05-22 06:45:53 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:

Description paul 2005-06-21 13:29:20 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

Description of problem:
When you run /etc/init.d/xinetd status, the script always returns '0' regardless of whether it is running.

This can be fixed by setting RETVAL=$? in the 'status' part of the case statement

Version-Release number of selected component (if applicable):
xinetd-2.3.13-4

How reproducible:
Always

Steps to Reproduce:
1./etc/init.d/xinetd start
2./etc/init.d/xinetd status
3.echo $?
#> 0
4./etc/init.d/xinetd stop
5./etc/init.d/xinetd status
6.echo $?
#> 0  

Actual Results:  Always returns 0

Expected Results:  non-zero

Additional info:

Comment 1 Matthew Miller 2006-07-10 20:29:09 UTC

Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Comment 2 Jan Safranek 2007-05-22 06:45:53 UTC

This bug has been fixed in xinetd-2.3.14-9.fc6