(note, for some insane reason
VB blocks anything with a $ in front of it... so i HAD to not use the code tags)
Here's what i did so far to get limiting, working:
after following the normal installation steps do the following:
copy the code above into limiter.c file in wherever your BOINC directory is.
compile it:
gcc limiter.c -o limiter
now lets go and edit an init.d script:
nano -w /etc/init.d/boinc
first, you will see a lot of defined values. Take a moment and add one more to it
MAX_FREQ=60
now go to section that says
echo -n "Starting BOINC client as a daemon: "
su $BOINCUSER -c "$BOINCEXE $BOINCOPTS" >>$LOGFILE 2>>$ERRORLOG &
sleep 1
PID=`pidof -s -x -o $$ -o $PPID -o %PPID $BOINCEXE`
if [ $PID ]; then
[ -d $LOCKDIR ] && touch $LOCKDIR/boinc
add this just after that line
# rather dirty way of doing this
./limiter $PID $MAX_FREQ &
this will start the limiter when you start the service
now only to kill it when you are done
go to section that says:
cd $BOINCDIR
if [ ! -f lockfile -a ! -f $LOCKDIR/boinc ] ; then
echo -n "BOINC is not running (no lockfiles found)."
echo_success
else
echo -n "Stopping BOINC client daemon: "
killproc $BOINCEXE && echo_success || echo_failure
# clean up in any case
rm -f $BOINCDIR/lockfile
rm -f $LOCKDIR/boinc
now lets add one more line to it
killall limiter
save, restart service, do a ps -ef f, make sure limiter is in there, do a top, to make sure that whatever boinc is doing, it is not exceeding whatever max percent utilization, and we are in game

----------------
Microsoft, the leader in using innovative tactics to promote irksome experience, coupled with antiquated technology that's held together by a pyramid of makeshift afterthoughts.
Apple, the leader in using irksome tactics to promote innovative experience, coupled with an antiquated core that's enhanced by state-of-the-art afterthoughts.
Linux, the leader in not using any tactics to promote user-defined experience, coupled with state-of-the-art core enhanced by innovative afterthoughts.
