Bug 189101

Summary: rpc.lockd not locked down correctly by /etc/sysconfig/nfs
Product: [Fedora] Fedora Reporter: Ian Laurie <iml>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-07-01 10:10:37 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Ian Laurie 2006-04-16 02:24:33 EDT
Description of problem:
rpc.lockd is not locked down correctly by the configuration file
/etc/sysconfig/nfs.  For example:

# /etc/sysconfig/nfs

Won't lock down rpc.lockd after a boot.  However it typically will if you issue
a "service nfs restart" command.

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

How reproducible:

Steps to Reproduce:
1. Create above /etc/sysconfig/nfs file.
2. Reboot the system.
3. Issue "rpcinfo -p" command.
4. Issue "service nfs restart" command.
5. Issue "rpcinfo -p" command again and observe the difference.
Actual results:
rpc.lockd not locked down after a boot.

Expected results:
It should be locked down.

Additional info:

The problem is that although the control script /etc/rc.d/init.d/nfs references
the variables LOCKD_TCPPORT and LOCKD_UDPPORT, the /etc/rc.d/init.d/nfslock
script does not.  It seems what is in the nfs script isn't good enough....
perhaps because at the time the nfs script is trying to get rpc.lockd to lock
down its ports, rpc.lockd isn't running yet (or something like that as it works
with a restart).

This problem is in RHEL4 as well but was fixed with a patch.  The same patch
fixes FC5 also.  See bug 162133 for details.
Comment 1 Steve Dickson 2006-07-01 10:10:37 EDT
fixed in nfs-utils-1.0.8-3