Seti and Smoothwall

[Geomagick]

I have just set up a smoothwall firewall which is running great.

However I am very new to Linux of any sort and would like to use the spare CPU cycles to good effect and run SETI.

The system is a dual P2 so I would quite like to run 2 sessions of SETI.

Any help would be greatly appreciated.

 

[BlackMountainCow]

I'm sure that one of our old timer SETI guys can help you out on this! (bumperama)! 😉

 

[amdxborg]

Could have helped with SETI for Windows, but sorry rever ran it on Linux...

Someone will know! 😉

 

[Freewolf]

Oh Polo where are you ?

 

[soni]

Download the seti client for your platform,.
Un tar, to a folder.
Copy folder, since you have 2 cpus you need to instances.
chmod 774 seticlientfilename
run ./setiname in each folder under a seperate cli, I usually use <ctrl><alt><f2-f6>
it should ask for the rest

 

[Coolkid]

What soni is suggesting should work fine 🙂
Only problem is that the Smoothwall kernel doesent support multiple CPU systems 😕
Search around on the Smoothwall forums, I think someone posted a modified kernel there 🙂

Thw only other problem you might have would be with the Squid proxy, i found when running S@H on my Smoothie, Squid wouldnt cache anything.
Not sure if thats because S@H is hogging all the cpu time (unlikely), or it was just lack of ram (64mb).
I didnt bother to pursue it as its just a P166 machine.

Anyway, good luck! 😀

 

[Polo]

1) In your home directory (assuming it's /home/george) create two folder, one for each CPU :
cd
mkdir SETI
cd SETI
mkdir CPU0
mkdir CPU1
2) Download the linux SETI client : V3.03 is faster and you can grab it here
(Note : it's not zipped... just rename it setiathome this way : mv setiathome.zip setiathome)
3) make it executable : chmod 755 setiathome
4) and put one copy in each folder CPU0 and CPU1 : cp setiathome /home/george/SETI/CPU0/
cp setiathome /home/george/SETI/CPU1/
5) Now time to launch SETI for the first time...
cd /home/george/SETI/CPU0/
# If you don't use a SETI proxy then just type
./setiathome
# Else (if you use a SETI proxy (my.seti.proxy listening on port 5517 in the example)) then type
./setiathome -proxy my.seti.proxy:5517
--> SETI will ask you to enter your SETI e-mail adress and download a new work_unit. When done wait a minute to be sure and type CTRL C to terminate the setiathome process.
You now have all the needed files in your work directory.
Then repeat this for cpu1.
6) Launch setiathome at boot time this way (You'll have to be root to do this) :
You'll have to modify your /etc/rc.local file : vi /etc/rc.local
Then add these lines at the bottom of the file :
# Launch SETI@Home
cd /home/george/SETI/CPU0
./setiathome -proxy my.seti.proxy:5517 -nice 19 &amp;
cd /home/despretz/SETI/CPU1
./setiathome -proxy my.seti.proxy:5517 -nice 19 &amp;
7) That's all folks ! 🙂
You now could use KSetiWatch to monitor your two processes under KDE.

Hope this helps. 🙂

 

[Geomagick]

Thanks for that, I'll give it a try.

Should really go and learn more about linux first.

 

[JWMiddleton]

Originally posted by: George Powell

Should really go and learn more about linux first.

Hey George,

Many Linus/Unix commands have a DOS equivelent , so if you are familar with DOS there is a book called Unix for DOS users. It builds on what you know already from DOS. Linux/Unix commands have many more options, but the basics are just that, basic. The only one in Polo's instructions that is really diff is chmod or change mode. It equates to attrib in DOS, but is a lot more involved.

Also note the period before the / in the line to execute the programs. The ./ combo has confused a lot of new users, me included. You can see the file in the dir, but you can't execute it with out that, or a proper path.

He also used vi...that is an editor. Not user friendly. Get the book! lol

Good luck!

 

[Geomagick]

thanks.

I was brought up on DOS so that should be a great help