We've expanded our news coverage and improved our search! Visit
oreilly.com for the latest or search for all things across O'Reilly!
| Weblog: |
|
Blame the last man standing?
|
| Subject: |
|
Rendezvous ill accused probably. |
| Date: |
|
2003-07-15 17:35:59 |
| From: |
|
anonymous2
|
Response to: Rendezvous ill accused probably.
|
|
"There were network problems initially, but by the end everything was working well (when you could get an IP address from DHCP). IOW, no rendezvous issues in a much heavier wireless network situation."
I was also at WWDC. One time I enabled Rendezvous in iChat, and the next thing I knew, the "mDNSResponder" Multicast DNS responder process was eating my PowerBook G4 17" CPU alive. 75% or thereabouts of the CPU was being eaten by this thing. I hate to say it, Stuart, but even if Rendezvous wasn't the cause of the problem with the network(s), it sure was a problem on my CPU. I immediately turned it off in iChat and things returned to normal.
|