Debian & SETI

[Nemesis77]

Stupid questions, I know... How to get SETI run properly in Debian? I can install it without any problems, and I can even run it. But I would like it to run automatically on startup (can't remember how to do it right now). Also (this is the main problem), I have a 120MHz web/Samba-server, that just begs to run SETI 🙂. If I log on to it via SSH, I can start SETI, but when I disconnect, it kills the process.

 

[Poof]

Stupid questions, I know...

Absolutely NO question is stupid!!!!!! 🙂

How to get SETI run properly in Debian? I can install it without any problems, and I can even run it. But I would like it to run automatically on startup (can't remember how to do it right now). Also (this is the main problem), I have a 120MHz web/Samba-server, that just begs to run SETI 🙂. If I log on to it via SSH, I can start SETI, but when I disconnect, it kills the process.

People do it different ways but you can add the command in either boot.local or rc.local (or whatever Debian calls it), by adding a startup like:

nohup /pathtosetiathome/setiathome {parameters} &

Note the "nohup" (which will become a file that tracks your console output) and also note the "&" <---this being VERY critical to have there, ESPECIALLY if you want to start SETI up at boot.

In general, if you're sshing in, you can also do the above. The "&" allows the process to fork into the background so when you exit the ssh session, the process will continue to run.

You can alternately shunt any screen output to /dev/null, usually like:

nohup /pathtosetiathome/setiathome {parameters} > /dev/null 2>/dev/null &[/b]

[EDIT: You can find a bunch of other options and stuff listed in the readme - if you grab the tarred client! 🙂]

 

[Nemesis77]

thanks 🙂! That did the trick!

 

[TwoFace]

another thing that works wonders is a little program called screen (one of my favourites still THANKS to SyZ for pointing me at it long ago) and since you're running debian....

1. ssh to your debian box, su
2. apt-get update
3. apt-get install screen
4. logout
5. cd to your seti directory (assuming you run seti as user and not root)
6. screen ./setiathome_blahdi_blahdi_blah -proxy whateveryoursetiqipisifyouhaveone:someport -nice 19
7. CTRL+a+d to get out of the screen
8. screen -r to get back to see your seti client

You can of course use multiple screens but then you have to supply a pid when doing screen -r (don't worry if you do a plain one first you'll see the pids you have to choose from) I use this to run seti, pproxy and basically anything I'd ordinarily run with & but I still want to be able to see the output. 😀

TF