Bug 31802 - NFS Locking not working due to rpc.statd
Summary: NFS Locking not working due to rpc.statd
Status: CLOSED DUPLICATE of bug 31801
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-server   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
high
high
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-14 21:26 UTC by Steven McDowall
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-03-14 21:27:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
strace showing statd system calls (and failures) (27.63 KB, text/plain)
2001-03-14 21:27 UTC, Steven McDowall
no flags Details

Description Steven McDowall 2001-03-14 21:26:20 UTC
rpc.statd is basically broken due to the new security "enhancements" added
in RH 7.0.  In effect, any lock requests to rpc.lockd fail because 
rpc.statd can't "monitor" anything.  This is due to rpc.statd not being
able to do just about anything after it starts (like accessng files).

The reason is that rpc.statd now chdirs to /var/lib/nfs/statd (which is
fine), then CHROOTS to "." !! Well, needless to say after the chroot
not much works since it can no longer access /etc, /usr/lib, etc.

I would suggest either removing the questionable "chroot" call or
making sure when installing that a full "anon ftp" sort of environment
exists under /var/lib/nfs/statd

Comment 1 Steven McDowall 2001-03-14 21:27:32 UTC
Created attachment 12667 [details]
strace showing statd system calls (and failures)

Comment 2 Michael K. Johnson 2001-03-14 22:08:43 UTC

*** This bug has been marked as a duplicate of 31801 ***


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