Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Not a new problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Not a new problem
Authored by: raw on Nov 21, '02 12:12:28PM

I've had this problem (lookupd stalling) since 10.0.x (when I moved from Linux to OS X). I researched the problem at the time I found references to this problem in OS X Server 1.x (on Stepwise) and NeXT (somewhere). And there were multiple entries in the Darwin bug-tracking system. I've followed every workaround suggestion I could find and still haven't licked the problem.

Of course, I blame myself. :-)

This is because I am using non-Server OS X as my SOHO server: my own BIND (previously my build, now the Apple-supplied version), Apache (ditto), Postfix (instead of sendmail), uw-imapd, and stunnel.

So I get pretty heavy DNS use and I think that makes the situation worse. I would hope that "normal" users wouldn't have this problem, but perhaps that isn't the case.

It is a pain but seems to have gotten better with each release. (In 10.1.x I even got into a state where only a physical reset worked. Yuck.) But I sure hope Apple smashes this bug soon....

Cheers,
Richard



[ Reply to This | # ]