On Thu, Dec 22, 2005 at 09:21:26PM -0500, rpeterso wrote:
> 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.
BTW, the behaviour is that all files appear to be locked. In vi, for
example, when I try to edit the file 'test' below, it says:
"test" [FILE BEING MODIFIED BY ANOTHER PROCESS] 1 line, 31 characters
on tru64 alpha:
% ls -al
total 12
drwxrwx--- 2 root kmw 4096 Dec 22 20:22 .
drwxr-xr-x 6 root system 4096 Dec 22 08:22 ..
-rw-rw-r-- 1 root kmw 31 Dec 22 21:27 test
% groups
accntmgr kmw ...
Best.
--
Ron Peterson
Network & Systems Manager
Mount Holyoke College
http://pks.mtholyoke.edu:11371/pks/lookup?search=0xB6D365A1&op=vindex
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
