[RC5] Something dnetc needs

Dennis Lubert plasmahh at gmx.net
Mon Mar 18 20:32:33 EST 2002


At 11:27 16.03.02 -0600, you wrote:
>OK, short of being able to monitor temperatures from the motherboard, what
>the client needs is the ability to assign a duty cycle.  The default would
>be 100%, but you should be able to set it to anything you want.  As machines
>run hotter and hotter, the risk of problems being blamed on dnetc increases.
>If you could set it to a 90% duty cycle, with a halt issued for the other
>10%, you could drastically decrease the number of machines with thermal
>problems.  I wouldn't think that this would be terribly difficult to
>implement.  Thoughts?

I agree to this need, because of another reason. In our company, and at 
university I am allowed to run processes which fit the following 
requirements :
either total running time < 30min.
or average cpu consumption is at ~ 30%

so I can't run dnetc on these machines, or only for 30mins a day

>Colin Hildinger
>
>--
>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 mailing list