Messages in this thread | | | Subject | Re: nfs insecure_locks / Tru64 behaviour | From | Trond Myklebust <> | Date | Fri, 23 Dec 2005 16:00:25 +0100 |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |