Bug 220144 - /etc/init.d/ypserv status reports wrong status
Summary: /etc/init.d/ypserv status reports wrong status
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: ypserv   
(Show other bugs)
Version: 4.2
Hardware: i386 Linux
Target Milestone: ---
: ---
Assignee: Steve Dickson
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2006-12-19 06:43 UTC by Clotho Wing Yee Tsang
Modified: 2015-01-08 00:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-21 02:40:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Clotho Wing Yee Tsang 2006-12-19 06:43:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv: Gecko/20061025 Firefox/

Description of problem:
No matter ypserv is started or stopped, "/etc/init.d/ypserv status" always returns status '0'.

I find that it can be fixed by adding a line in /etc/init.d/ypserv:
The line "RETVAL=$?" should be added after "status ypserv".

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

How reproducible:

Steps to Reproduce:
1. Stop ypserv by command "service ypserv stop"
2. Run "service ypserv status"
3. Run "echo $?"

Actual Results:
0 is output

Expected Results:
A non-zero number should be output

Additional info:

Comment 1 RHEL Product and Program Management 2006-12-21 02:24:27 UTC
The component this request has been filed against is not planned for inclusion
in the next update. The decision is based on weighting the priority and number
of requests for a component as well as the impact on the Red Hat Enterprise
Linux user-base: other components are considered having higher priority and the
number of changes we intend to include in update cycles is limited.

Comment 2 RHEL Product and Program Management 2006-12-21 02:40:52 UTC
Product Management has reviewed and declined this request.  You may appeal this
decision by reopening this request. 

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