Ken Hornstein <[EMAIL PROTECTED]> writes:
> It always seemed to me that the right solution was to change the cache
> manager so that a stat() of a mountpoint in /afs didn't cause you to
> contact that cell. There's was even some code that was #ifdef'd out in
> the cache manager that claimed to do that (but it was for NeXTStep, so
> I suspect that it hasn't been maintained :-) ).
That has some interesting history; it was pretty much mandatory to make
that change for NeXTSTEP since otherwise you'd immediately hang the NeXT
file browser, which was pretty much always started. For whatever reason,
it just loved stating things in all directories up from your home
directory to the root level.
We locally hacked around that by mounting AFS on /.afs and creating a
separate /afs directory with some appropriate symlinks to the local cells.
Really ugly.
I think the last of our AFS-using NeXT cubes are gone now.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
