Topic: SETI@Home ran from an Ibay

[Lee Roy]

Can some one give me a hand in running SETI@home from an ibay, I keep getting a core dump when I try to run it.

TIA
Lee Roy

[Rob Hillis]

Lee Roy wrote:

> Can some one give me a hand in running SETI@home from an
> ibay, I keep getting a core dump when I try to run it.

I personally run it from it's own user account.  Simply copy the necessary files into ~seti, make sure you chown everything, and it *should* run.

I never had core dump problems when trying to run SETI@Home, and my first attempt was via an ibay... I'd also check to see that you've got a good copy of the program...

[Lee Roy]

Rob, ok, I have it runing in /seti/setiversion# , working fine, but I'm new to
linux, what does > "make sure you chown everything" mean?


Even Newbies Need Linux
thanks
Lee Roy

[Rob Hillis]

Lee Roy wrote:

> Rob, ok, I have it runing in /seti/setiversion# , working
> fine, but I'm new to
> linux, what does "make sure you chown everything" mean?

If you've created a new user account for SETI@Home (as I would reccomend) then make sure you modify the ownership of the SETI files to the user you created.

Maybe it's time for me to try putting together a HOWTO on running SETI@Home... I'd try to package it, but my own knowlege of Linux isn't good enough for that...

Simple instructions... (better ones pending until later)

Create yourself a user "seti" using the E-Smith manager.

Download the SETI@Home client... I'm using ftp://ftp.cdrom.com/pub/setiathome/setiathome-3.03.i686-pc-linux-gnu-gnulibc2.1.tar  Store it in the SETI user's root directory.

Login as root, and type the following commands...

cd ~seti
cat setiathome* | tar x
mv setiathome-3.03.i686-pc-linux-gnu-gnulibc2.1/setiathome .
rm setiathome-3.03.i686-pc-linux-gnu-gnulibc2.1/ -rf
./setiathome

When you run the last command, you'll be taken through the setup process for SETI@Home.  Finish this process.  Once SETI has finished downloading it's first packet (fairly important for the next step) press CTRL-C to kill the client.  Next type the following commands...

echo nice -n 15 ./setiathome > runseti
chmod 700 runseti
chown seti:seti *

Now create /etc/e-smith/templates/etc/crontab/seti with your favorite editor and put the following contents in it...

----8><----- (all one line!)
# SETI@Home
*/10 * * * * seti /home/e-smith/files/users/seti/runseti 2>/dev/null >/dev/null
----8><-----

Then run /sbin/e-smith/expand-template /etc/crontab and within the next 15 minutes, you'll have yourself an invisible SETI client doing it's work...

(A very quick and very dirty SETI HowTo...)

[Lee Roy]

Rob, i'm not sure of the cron tab files.
this:
----8><-----
# SETI@Home*/10 * * * * seti /home/e-smith/files/users/seti/runseti 2>/dev/null >/dev/null
----8><-----

or

all one line means:  -------8><-------#SETI@HOME*/10****XXXXXXX------8><-------

or the way i had it above that?   sorry about the having to give cron tab lessons.

Lee Roy
http://dogbox.homeip.net

[Rob Hillis]

Lee Roy wrote:

> Rob, i'm not sure of the cron tab files.
> this:

My apologies for not being entirely clear...  The crontab entry should be the following...

Line 1 containing "# SETI@Home" (which is simply a comment so that you know what you're looking at)

Line 2 containing all of the following on the one line...

*/10 * * * * seti /home/e-smith/files/users/seti/runseti 2>/dev/null >/dev/null

I hope this clears things up...

[Lee Roy]

i'll let you know in about 15 mins.   heheh   thanks Rob

Lee Roy

[Lee Roy]

Rob, i can see it start but it does not keep running... i can see that it does this about ever 10 mins. it starts and shuts right back down. i'm useing e-smith System Monitor mod and watching the cpu state/load to see this start and stop. i can send a screen cap of it if need be. you earlyer post on the dirty how to was follower with cut and past so i would not it up mess up. any more help you can give would be great.

thanks
Learning Linux
Lee Roy

[Lee Roy]

on a few e-smith mods i have installed, this is the last thing that gets done to update the config files. does this need to be done to get seti to keep running?

/sbin/e-smith/signal-event console-save


thanks
will newbies ever learn
Lee Roy

[Lee Roy]

ok.. that last little: /sbin/e-smith/signal-event console-save   did it, it now started on it's own and shows up in the cron tab logs as:

Sep 14 00:50:00 dogbox350 CROND[14383]: (seti) CMD (/home/e-smith/files/users/seti/runseti 2>/dev/null >/dev/null)


you have been a very big help,  thanks you!!


See, newbies do learn
Lee Roy
http://dogbox.homeip.net

[Rob Hillis]

Lee Roy wrote:

> on a few e-smith mods i have installed, this is the last
> thing that gets done to update the config files. does this
> need to be done to get seti to keep running?
> /sbin/e-smith/signal-event console-save

Not in this case.  Cron automatically rereads the /etc/crontab file when it detects that it's changed, so it should start running automatically.  On the question of why the client is stopping, you might want to edit /etc/crontab directly and remove the diversions to /dev/null as a test only... what will happen is that cron will start mailing you the output of the SETI client each time it finishes, and is good for debugging info...