From: Ron Peterson <rpeterso@MtHolyoke.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs insecure_locks / Tru64 behaviour
Date: Fri, 23 Dec 2005 09:39:50 -0500 [thread overview]
Message-ID: <20051223143950.GA1330@mtholyoke.edu> (raw)
In-Reply-To: <1135345813.8167.155.camel@lade.trondhjem.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 859 bytes --]
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. :(
Skøl.
--
Ron Peterson
Network & Systems Manager
Mount Holyoke College
http://pks.mtholyoke.edu:11371/pks/lookup?search=0xB6D365A1&op=vindex
next prev parent reply other threads:[~2005-12-23 14:39 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
2005-12-23 13:38 ` Ron Peterson
2005-12-23 13:50 ` Trond Myklebust
2005-12-23 14:39 ` Ron Peterson [this message]
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=20051223143950.GA1330@mtholyoke.edu \
--to=rpeterso@mtholyoke.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.