[116] in Info-AFS_Redistribution
problems with AFS on the NeXT
daemon@ATHENA.MIT.EDU (erikkay@MIT.EDU)
Sat May 11 15:28:28 1991
From: erikkay@MIT.EDU
To: info-afs@transarc.com
Date: Sat, 11 May 91 14:24:30 EDT
Hi all. here at MIT, I've been trying to get AFS 3.1 working on the
NeXT. It seems to do pretty well, except for a couple of really
annoying problems. Anybody have any answers for these?
1) When doing anything with NFS when the AFS kern_loader is loaded, I
get the following error messages spewing into the private/adm/messages
file with virtually every packet of NFS that goes through. When I
tried to do a build over NFS, the system lost, becuase messages filled
up the disk.
Nfs2AfsC: which=%d
Nfs2AfsC-4: No first; second?(%x)
The only solution I found was to edit the binary, and to put a null at
the beginning of each of these strings.
2) Some directories just lose when I try to access files within them.
The process trying to access the file(s) goes into uninterruptible
disk wait and hangs forever. i can access these directories from
other platforms.
3) The browser hangs for a long time if i look in /afs. It takes a
couple of minutes becuase it tries to stat every directory in the
browser. I know this isn't really and afs problem, but has anybody
found a solution (other than not looking at /afs) ?
4) Certain programs which aren't run as the user's uid (but as root
instead), try to access the ~/.NeXT directory, both trying to lock
files in it, or trying to write to files within it. The only solution
I found was to make it accessible to system:anyuser. Obviously not a
good solution!
thanks in advance,
-Erik Kay
