Adam Megacz wrote: > The real problem is that -- because of the way the Finder works -- the > AFS client was severely crippling his machine even when he wasn't > trying to use AFS. If it had simply been a matter of AFS not working, > that would have been a minor inconvenience. But from his perspective, > he installed this strange software he's never heard of, and all of a > sudden he couldn't do things he was doing before. Really bad.
If AFS is having such a negative impact on the functionality of the system then either there is a serious bug in AFS or a bug in the Finder. Both Apple and OpenAFS will want to have bug reports filed so that the problem can be fixed. As Apple confirmed in this thread, only by having users submit bugs to Apple can we obtain the necessary resources to get these problems addressed. > Yeah, if it had just been a matter of "I can't access stuff in /afs", > I would have been more patient. I've been through the server-log > drill before, it's no sweat. This is the first time in this thread that you have mentioned this. In the future please describe the problem you are attempting to solve instead of asking how to implement what you believe is the work around. Then we can provide you on target advice. > I take pains to mention that, at the end of the day, I fault Apple's > Finder design for allowing unresponsive network filesystems to cause > so much trouble for people trying to do non-network-filesystem-related > work. I consider it more or less a miracle that there's a MacOS AFS > client at all, and I'm grateful for that. Apple is working on the Finder issues. Please file a bug report with them for this problem and make sure that Berkeley's Apple representative knows that fixing it is important to your department. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
