Seems to be that sometimes lookupd crashes and thus the Mac OS X System becomes unresponsive. This bug is around for years now – funny thing is that I never ever ran into it – but after my girl is now using the system for vb.net development – she ran into it four times.So good thing is there is a fix, as you can see in the explanation for this issue:
Lookupd is the lookup and caching daemon responsible for handling NetInfo, DNS, and other such requests. Applications typically do not access lookupd directly, but rather, use standardized library functions (such as gethostbyname for DNS) which access lookupd on the application’s behalf.Lookupd has a bug (rdar://3632865) in its cache cleanup code that causes it to randomly crash. CrashReporter, the system crash log agent, does not properly handle lookupd crashes, and as a result, when lookupd crashes, the process is not terminated. Since lookupd has not terminated, mach_init does not respawn lookupd. From this point, any application that attempts to access lookupd, either directly or indirectly, will hang.Once lookupd stops responding, it becomes difficult, but not impossible, to recover the system to a usable state. One technique which works, but is not recommended (for obvious reasons), is to leave a root shell running and
killall -9 lookupd when it becomes obvious that lookupd has died (sudo does not work, since it requires lookupd’s services, as does opening a new terminal window).
Additional informations can be optained, here:http://fivepoundsflax.blogspot.com/2006/11/is-your-lookupd-crashing-its-years-old.htmlÂ http://dshadow.com/software/unlockupd/The bug number is apparently 3632865 in Apple’s bug-tracking system, “radar”. The rdar url above is usable by Apple folks, only. There’s no way for the public to see the details of that bug number. Joel wrote a little article about this problem as well.
technorati tags:apple, macosx, bug, lookupd