Topic: SETI@HOME

[Chaloner Hale]

Installed setoathome last night. Tries tp run every 10 minutes as shown in var/log/cron. It will run manually if started by hand, and can be seen using 50% of my CPUs when running. How do I keep it going automatically???

Thanks, and Merry Xmas,

Chaloner Hale

[Thor Anthrax]

http://setiathome.ssl.berkeley.edu/linux_script

[Chaloner Hale]

Thanks Thor. Do I get rid of the previous crontab entries? I really have no idea of what to do with this file.

Merry Xmas,
Chaloner Hale

[Thor Anthrax]

You have to delete the crontabs yourself.

Download the file and edit the values of where seti is on your disk. Then use ./start start to start the client.

I've added this to my startup procedure in /etc/rc.d/rc.local

[Chaloner Hale]

Thanks again.

I saved the file as seti in /etc/init.d and tried to start it with ./set start (not ./start start) and get "bash ./seti: No such file or directory".

Does this mean I have bad characters in the file? I set SETI_CLIENT_DIR and SETI_DIR to /home/e-smith/files/users/seti/bin where my seti files are located.

If you think it is my file, can you email a good one please???

Thanks,
Chal

[Thor Anthrax]

I made a new HOWTO for you (and others)

http://sme.nightspirit.nl/SETI@home.html

[Rob Hillis]

Thor Anthrax wrote:

> I made a new HOWTO for you (and others)
> http://sme.nightspirit.nl/SETI@home.html

Two immediate suggestions...

I run SETI@Home in it's *own* user environment.  Create a user "seti" from the control panel, and install everything in ~seti.

I personally run a cron job to re-launch S@H.  This allows me to run the SETI client as it's own user, which has security advantages.  (Running anything as root has inherent security risks, especially if the S@H client is compromised or replaced)

The other advantage to running S@H as it's own user is that it will automatically be backed up and restored by backup to desktop/tape.