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 14:50:12 +0100 [thread overview]
Message-ID: <1135345813.8167.155.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20051223133801.GA9321@mtholyoke.edu>
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:
[trondmy@longyearbyen trondmy]$ id
uid=520(trondmy) gid=100(users) groups=10(wheel),100(users)
[trondmy@longyearbyen trondmy]$ ls -al
total 0
drwxr-xr-x 5 trondmy users 36 Dec 23 08:44 .
drwxr-xr-x 3 root root 20 Jun 17 2005 ..
drwxr-x--- 2 root users 18 Dec 23 08:47 d
drwxr-xr-x 8 root root 68 Dec 5 01:11 gnurr
drwxr-xr-x 2 trondmy users 30 Nov 23 10:38 tmp
[trondmy@longyearbyen trondmy]$ ls -al d
total 4
drwxr-x--- 2 root users 18 Dec 23 08:47 .
drwxr-xr-x 5 trondmy users 36 Dec 23 08:44 ..
-rw-r--r-- 1 root root 6 Dec 23 08:47 hello
[trondmy@longyearbyen trondmy]$ cat d/hello
hello
Cheers,
Trond
next prev parent reply other threads:[~2005-12-23 13:51 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 [this message]
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=1135345813.8167.155.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®