As I mentioned, it happens on my home systems with afp mounts, all running 10.4.7. Right now I'm at about 10 min with a beachball in Tiger. The remote machine is alive and well. I get the same hang in a terminal window if I try and ls the afp mount. Ctrl-C doesn't work on the ls command. Apple seems to be blocking signals and then letting processes hang. I'm now at 20 min. Finder is hung, terminal is hung. Finder won't relaunch. Trying to save work in other programs hangs. This is totally inexcusable behavior. It seems pretty clear that there is a system call related to reading a directory that blocks signals and hangs. If this is a fix I'd like to see a real bug. -John On Jul 30, 2006, at 11:10 PM, Enrico Franconi wrote: > > On 31 Jul 2006, at 06:36, John Daschbach wrote: >> At work, running the latest 10.3 > > (...) > >> Any directory with a symlink to an AFS file system would hang the >> whole system once the AFS link was no longer valid. Apparently OS >> X has no time out on scanning a directory, so when it hits a dead >> link it waits forever for it to return a list of files. > > This was a known bug that has been fixed (with a timeout) in Tiger. > --e. > _______________________________________________ > X4U mailing list > X4U at listserver.themacintoshguy.com > http://listserver.themacintoshguy.com/mailman/listinfo/x4u > > Listmom is trying to clean out his closets! Vintage Mac and random > stuff: > http://search.ebay.com/_W0QQsassZmacguy1984