Re: nfs insecure_locks / Tru64 behaviour

[Ron Peterson <rpeterso@MtHolyoke.edu>]

On Fri, Dec 23, 2005 at 09:37:55AM +0100, Trond Myklebust wrote:
> On Thu, 2005-12-22 at 21:21 -0500, Ron Peterson wrote:
> 
> > Why it doesn't work .. I dunno.  My current best guess is that the
> > manner in which the insecure_locks option in /etc/exports is applied to
> > directories isn't quite right.
> 
> insecure_locks has nothing at all to do with directories. It has to do
> with the NLM protocol, which is used by NFSv2/v3 to implement posix
> locks.
> Directory locking is an entirely separate matter, and is not part of the
> NFS protocol (the server will take care of locking the directory when it
> needs to modify it without any extra help from the client).
> 
> IOW: your problem here has nothing to do with insecure_locks, and
> everything to do with your setup. Please double-check that the gid
> mappings for the group 'kwc' in /etc/groups match on the client and
> server, and note that the default root squashing means that your root
> account will get mapped to the user with uid -2 and gid=-2

The gid's of the kmw group match on both sides.  The problem happens
whether root squashing is on or off.  Unless the execute bit for 'other'
is turned on for the parent directory, the file appears to be locked
when being accessed from the nfs client (tru64) side.

My theory may be wrong, but the problem still exists.

Best.

-- 
Ron Peterson
Network & Systems Manager
Mount Holyoke College
http://pks.mtholyoke.edu:11371/pks/lookup?search=0xB6D365A1&op=vindex