[SETI] Anyone using Crunch3rs SSE3 optimised Linux apps?

[Berserker]

I'm getting quite a few results reporting no consensus on one of my Core2 Linux boxes. Is anyone else seeing these?

So far, I've had a few of these subsequently validate OK, but just want to make sure I'm not returning duff results.

 

[dunc]

I am using cruncher's version <2.4_Linux32_kernel_2.6_Intel_SSE3_FIXED> on 3 boxes without any apparent consensus issues. I did check through a bunch of results and didn't find any. Doesn't mean there aren't any tho.

My boxes are not overclocked.

Dunc

 

[Berserker]

Can you give me the URL for the 'FIXED' version please. That's clearly what I'm missing. Thanks.

Edit - no matter - found here.

Let's see if that helps.

 

[Berserker]

Oops - I'm running boinc as a boot-up task, and therefore as root.

If you do that, this 'FIXED' version likes to take over your system by elevating it's priority. Had to 'sudo' boinc to a non-privileged user to put a stop to that.

Anyone else who uses their Linux PCs for real stuff, beware.

 

[dunc]

I got around this by re-nicing boinc every 2 minutes in crontab.

Can't take credit for writing the script

#!/bin/sh
for i in `ps -u root o pid,comm | grep seti | awk ' { print $1 } '` ; do
Prio=`ps -u root o pid,ni,comm | grep $i | awk ' { print $2 } '`
if [ $Prio != "19" ] ; then
renice 19 -p `ps -u root o pid,ni,comm | grep $i | awk ' { print $1 } '`
fi
done
## end resah

*/2 * * * * root /home/user/boinc/BOINC/resah

Dunc

 

[Berserker]

Yeah, that works, but using a non-privileged account prevents the clients from elevating in the first place, so you don't need a cron job. It's also more secure.

If you start boinc from an init script, all you need is:

cd <path-to-boinc>; sudo -u <user> boinc -daemon

(after setting the right permissions on the boinc directory, of course).