Re: nfs insecure_locks / Tru64 behaviour

[Ron Peterson <rpeterso@MtHolyoke.edu>]

On Fri, Dec 23, 2005 at 02:45:25AM +0100, Trond Myklebust wrote:
> 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?

Yep.

Why it doesn't work .. I dunno.  My current best guess is that the
manner in which the insecure_locks option in /etc/exports is applied to
directories isn't quite right.

Best.

-- 
Ron Peterson
Network & Systems Manager
Mount Holyoke College
http://pks.mtholyoke.edu:11371/pks/lookup?search=0xB6D365A1&op=vindex