Bug 441605 - /etc/init.d/nfslock status gives incorrect return code
/etc/init.d/nfslock status gives incorrect return code
Product: Fedora
Classification: Fedora
Component: nfs-utils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-08 19:11 EDT by Michal Schmidt
Modified: 2008-11-24 12:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-24 12:11:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
return correct exit code from nfslock status (220 bytes, patch)
2008-04-08 19:11 EDT, Michal Schmidt
no flags Details | Diff

  None (edit)
Description Michal Schmidt 2008-04-08 19:11:01 EDT
Description of problem:

Quoting http://fedoraproject.org/wiki/Packaging/SysVInitScript :
If the status action is requested, the initscript must return the correct exit
status code, from this list:
 0:     program is running or service is OK
 3:     program is not running

"/etc/init.d/nfslock status" always returns 0. Therefore nfslock always appears
as running in system-config-services.

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

How reproducible:

Steps to Reproduce:
1. Make sure nfslock is stopped.
2. /etc/init.d/nfslock status ; echo $?
Actual results:
rpc.statd is stopped

Expected results:
rpc.statd is stopped

Additional info:
The attached patch applies on top of my patch from bug 441604.
Comment 1 Michal Schmidt 2008-04-08 19:11:01 EDT
Created attachment 301726 [details]
return correct exit code from nfslock status
Comment 2 Steve Dickson 2008-04-25 11:41:47 EDT
Fixed in nfs-utils-1.1.2-3
Comment 3 Bug Zapper 2008-05-14 05:09:55 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

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