From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ron Peterson <rpeterso@MtHolyoke.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs insecure_locks / Tru64 behaviour
Date: Fri, 23 Dec 2005 09:37:55 +0100 [thread overview]
Message-ID: <1135327075.8167.6.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20051223022126.GC22949@mtholyoke.edu>
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
Cheers,
Trond
next prev parent reply other threads:[~2005-12-23 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 13:36 nfs insecure_locks / Tru64 behaviour Ron Peterson
2005-12-22 23:21 ` Trond Myklebust
2005-12-23 1:39 ` Ron Peterson
2005-12-23 1:45 ` Trond Myklebust
2005-12-23 2:21 ` Ron Peterson
2005-12-23 2:32 ` Ron Peterson
2005-12-23 8:37 ` Trond Myklebust [this message]
2005-12-23 13:38 ` Ron Peterson
2005-12-23 13:50 ` Trond Myklebust
2005-12-23 14:39 ` Ron Peterson
2005-12-23 15:00 ` Trond Myklebust
2005-12-23 18:10 ` Bernd Eckenfels
2005-12-23 20:58 ` Trond Myklebust
2005-12-23 21:41 ` Bernd Eckenfels
2005-12-23 22:00 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1135327075.8167.6.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@MtHolyoke.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox