casa-mp-base
Public
Source
+Where <setidir> is the directory where the setiathome client is installed. This cron job will attempt to start the client at the top of every hour. If it is already running, the next invocation will do nothing. If the client is not running, it will be started. For more information on cron jobs see the crontab(1) manual page.--- README.orig Tue Dec 12 23:20:30 2000+++ README Mon Nov 22 00:06:00 2004-setiathome(1) User Commands Version 3.03 - December 2000--NAME- setiathome - the SETI@home client program--SYNOPSIS- setiathome [options]--DESCRIPTION- setiathome is the UNIX version of the SETI@home client.- It downloads radio telescope data from a network server,- analyzes the data looking for signals of extraterrestrial origin,- and uploads results to the server, repeating this cycle indefinitely.- See http://setiathome.berkeley.edu for more information.--FILES- The program generates several files with .sah extension- in the directory from which it's run.- These should not be modified.-- If you want to run multiple instances of setiathome- (on a multiprocessor machine, or on multiple machines- that share a filesystem) each one must be run in a different directory.- You can use symlinks for each directory to avoid duplication- of the binary image. e.g.:- ln -s cpu0/setiathome cpu1/setiathome-- setiathome uses a lock file (lock.txt) to prevent- multiple instances from running in the same directory.-- To finish up your current work unit, return your result, and not- download a new work unit, while the client is running, touch- a file named "stop_after_send.txt" in the client directory.- When the processing is finished, and the result sent, the client will stop.- *** Note this one file extension is .txt, while all other files used by- the client have extensions .sah ***-- The file "pid.sah" contains the process ID of the current instance.--RUNNING SETIATHOME- The first time you run setiathome it will interactively- ask you for email address, name, country etc.- This info is stored in a file and no interaction is- needed when you run the program subsequently.-- After this you can run setiathome in the background,- and direct its output to /dev/null if you like.-- setiathome can be freely stopped and restarted.- It saves its state in files, and will pick up where it left off.-- If you want setiathome to be started automatically, you can- set up a cron job. Add the following line to your crontab:-- 0 * * * * cd <setidir>; ./setiathome -nice 19 > /dev/null 2> /dev/null-- Where <setidir> is the directory where the setiathome client is installed.- This cron job will attempt to start the client at the top of every hour.- If it is already running, the next invocation will do nothing.- If the client is not running, it will be started.