Bug 248097 - ypserv service script report wrong status
ypserv service script report wrong status
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: ypserv (Show other bugs)
5.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-13 04:17 EDT by John Lau
Modified: 2008-08-02 19:40 EDT (History)
1 user (show)

See Also:
Fixed In Version: 2.19-6.fc7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-10-29 15:02:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
ypserv status patch (230 bytes, patch)
2007-07-13 04:17 EDT, John Lau
no flags Details | Diff

  None (edit)
Description John Lau 2007-07-13 04:17:41 EDT
Description of problem:

"service ypserv status" always return zero, no matter if the ypserv started or
not.It is because the return value of "status" function haven't been assigned to
$RETVAL so it doesn't go to the exit code.

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

ypserv-2.19-3 (in RHEL5) and any lower version in RHEL4 and RHEL3

How reproducible:
Always

Steps to Reproduce:
1.service ypserv status
2.echo $?
  
Actual results:

ypserv is stopped
0

Expected results:

ypserv is stopped
3
Comment 1 John Lau 2007-07-13 04:17:41 EDT
Created attachment 159133 [details]
ypserv status patch
Comment 2 Steve Dickson 2007-09-15 13:38:26 EDT
Fixed in ypserv-2.19-6.fc7
Comment 3 Fedora Update System 2007-09-18 18:31:09 EDT
ypserv-2.19-6.fc7 has been pushed to the Fedora 7 testing repository.  If problems still persist, please make note of it in this bug report.
Comment 4 Fedora Update System 2007-10-29 15:02:53 EDT
ypserv-2.19-6.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.

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