Bug 441605

Summary: /etc/init.d/nfslock status gives incorrect return code
Product: [Fedora] Fedora Reporter: Michal Schmidt <mschmidt>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-11-24 12:11:36 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
return correct exit code from nfslock status none

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: