[RC5] Something dnetc needs
Colin L. Hildinger
colin at ionet.net
Sun Mar 17 09:49:16 EST 2002
Right on the money. Heck, it's bad enough in an organization with 50 boxes.
Also, there's a difference between a cooling problem that's actually causing
instability and knowing that you're running something on the warm side of
what's best and wanting to tone it down a bit so you don't shorten component
lives. When not running dnetc, most office PC's just don't run nearly full
time (thus dnetc's usefulness) and don't generate the same quantity of heat.
Sure someone might do something that stresses it out occassionally, but it's
not heat soaked when they start the process, so thermal management is still
not a problem.
I believe the temp threshold option only works on Mac's, which are, uh,
less diverse than x86 PC's.
----- Original Message -----
From: "daniel carter" <hedonist at win.co.nz>
To: <rc5 at lists.distributed.net>
Sent: Sunday, March 17, 2002 1:31 AM
Subject: Re: [RC5] Something dnetc needs
> The point is an organisation with 10,000 boxes on their desktops is not
> going to go round and open every box to give the fan a dusting. Instead
> they will just say that dnetc causes instability in some machines
> (which is quite right) and thus outlaw it from the network.
> The duty cycle option would fix that.
> BTW, on some OSes the dnetc client does support a "Pause if processor
> temperature thresholds are exceeded" option.
> Seth H. Bokelman wrote:
> > I disagree,
> To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
> rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5