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 16:00:25 +0100 [thread overview]
Message-ID: <1135350025.8167.157.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20051223143950.GA1330@mtholyoke.edu>
On Fri, 2005-12-23 at 09:39 -0500, Ron Peterson wrote:
> On Fri, Dec 23, 2005 at 02:50:12PM +0100, Trond Myklebust wrote:
> > On Fri, 2005-12-23 at 08:38 -0500, Ron Peterson wrote:
> > > 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.
> >
> > Possibly, but that sounds like it might be a tru64 bug. As you can see,
> > a Linux client has no such problems:
>
> Not unlikely. I was hoping it was a bug that the insecure_locks options
> was meant to work around. Perhaps that's not possible. :(
As I said, insecure_locks has nothing to do with file access.
Cheers,
Trond
next prev parent reply other threads:[~2005-12-23 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 13:36 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
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 [this message]
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=1135350025.8167.157.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
all inboxes | Powered by JetHome®