Subject: Re: nfs insecure_locks / Tru64 behaviour
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ron Peterson <rpeterso@MtHolyoke.edu>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20051223013933.GB22949@mtholyoke.edu>
References: <20051222133623.GE7814@mtholyoke.edu>
	 <1135293713.3685.9.camel@lade.trondhjem.org>
	 <20051223013933.GB22949@mtholyoke.edu>
Content-Type: text/plain
Date: Fri, 23 Dec 2005 02:45:25 +0100
Message-Id: <1135302325.3685.69.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 931
Lines: 29

On Thu, 2005-12-22 at 20:39 -0500, Ron Peterson wrote:
> > As for your problem accessing files in the directory
> > 
> > drwxr-x---  2 root     system  4096 Dec 22 08:22 d/
> > 
> > as an unprivileged user on group 'kmw', the solution is obvious:
> > 
> > 'chgrp kmw d'
> > 
> > or
> > 
> > chmod a+x d
> 
> That's exactly the problem.  The first obvious solution doesn't work.
> Your second solution does.  The directory must have the execute bit set
> for other, or the the file cannot be edited, no matter who owns the
> directory (unless the owner/group is nobody/nogroup).

Why wouldn't the chgrp solution work? Isn't /etc/groups on the client
and server in sync?

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/