On Thursday 24 Sep 2009 12:07:05 Gabor Gombas wrote: > I thought the idea was to move all the scheduler fiddling that the init > script does currently into the core client. That way the init script > could be much simpler and people who just download BOINC from the web > would get the same features. But right now it seems both the core client > and the init script has to fiddle with the scheduler...
I never mentioned anything about init scripts. I sent a small patch to the mailing list which complements the current setpriority nice defaults, nice 19 for CPU tasks, nice 10 for GPU tasks. I considered downsides and I couldn't see any. That's it. Nothing more, nothing less. IMHO, what different distros do in their boinc init scripts is down to the distro. Dynamic nice priorities, scheduler policies, CPU affinities - if a distro or user wants to set them from an init script, that's fine. It actually works quite nicely for decreasing what would other wise be the default priorities set by the code, which can't increase them at runtime. Regards Clive -- Clive Messer <[email protected]> _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
