[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with find + AFS + acl="l"

From: Daniel Richard G.
Subject: Re: Problem with find + AFS + acl="l"
Date: Fri, 3 Nov 2006 17:06:41 -0500
User-agent: Mutt/1.5.9i

On Fri, 2006 Nov 03 18:30:00 +0000, James Youngman wrote:
> >
> >AFS in many respects disregards the Unix mode bits, giving primacy to ACLs.
> >If you could enumerate the ways in which a canonical path might not be
> >obtainable, I can test to see if any of them apply to AFS.
> A typical example I suppose is that ".." is not searchable (this does
> not prevent getcwd() working on all systems).  I can't think of
> another example right now.  Maybe there could be cases where some
> ancestor directory is mounted from an unreachable NFS server (while
> "." is a local filesystem or is mounted from a different, reachable,
> NFS server).

Okay, I've experimented a bit on AFS:

* Removing all ACL access on a parent directory changes nothing in cwd. 
  You can't cd into the parent directory, or anything below it, but if 
  you're already there, everything continues to work.

* chmod'ing directories (even cwd) to 000 has no effect whatsoever.

So there shouldn't be any problem there, and you certainly won't run
into AFS mount points inside of unreachable NFS trees (unless the root
directory is on NFS---in which case the system has bigger problems
anyway :-)

Is there any more information I can provide about AFS behavior?


NAME   = Daniel Richard G.       ##  Remember, skunks       _\|/_  meef?
EMAIL1 = address@hidden        ##  don't smell bad---    (/o|o\) /
EMAIL2 = address@hidden      ##  it's the people who   < (^),>
WWW    = http://www.******.org/  ##  annoy them that do!    /   \
(****** = site not yet online)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]