Re: "distccsched" eating cpu, running hot
Re: "distccsched" eating cpu, running hot
- Subject: Re: "distccsched" eating cpu, running hot
- From: Mark Lentczner <email@hidden>
- Date: Mon, 28 Feb 2005 08:56:59 -0800
A follow up to prior post on this issue:
On Jan 20, 2005, at 2:10 PM, Scott Lahteine wrote:
Turns out the "distccsched" process was running in a tight loop,
eating up processor and running up the temperature. I'm not doing any
distributed building at the time when this occurs.
On Jan 20, 2005, at 11:23 PM, Dix Lorenz wrote:
I have noticed it sometimes after I wake up the computer (Dual G5, 2
GHz). I filed a bug on 01-Jun-2004. It's Open/Analyze... :-(
I've nailed it: It happens when:
1) After you have done a distributed build. This leaves distccschedd
running, even if you quit Xcode.
2) Your network configuration changes so that the IP address of the
interface(s) distccschedd saw on start up are now different, then
distccschedd goes into 100% CPU mode.
So, for example, waking your computer from sleep, and it gets a
different IP address via DHCP -- this will cause the problem.
Turns out the fix is easy: Just quit the process. No need to restart
it - seems Xcode will do this next time it starts a distributedd build.
I use Activity Monitor (which I always have running anyway for the
Dock CPU meter) and I leave the Activity Monitor window set to "Active
Processes". When the problem occurs, distccschedd is there and Quit
works like a charm. (I suppose "killall distccschedd" in the shell
would work too... )
Should I file a bug on this, or do you Apple folks have it covered?
- Mark
Mark Lentczner
email@hidden
http://www.wheatfarm.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden