getting setiathome to load on start up

**hmiller68** · 01-20-2004, 06:44 AM

I have been trying to get setiathome to load on start up but cant seem to find which file to edit to get it to load on boot. Ive tried /etc/init.d/bootmisc and it loads there but goes no farther than the setiathome start up and I usually have to press control c to finish up
the boot and regretfully kill setiathome. what Im basically trying to do is get so I dont have to load it everytime i reboot. Any one know where to enter the line to get to do so.

**Stephen** · 01-20-2004, 07:41 AM

Originally Posted by hmiller68

I have been trying to get setiathome to load on start up but cant seem to find which file to edit to get it to load on boot. Ive tried /etc/init.d/bootmisc and it loads there but goes no farther than the setiathome start up and I usually have to press control c to finish up
the boot and regretfully kill setiathome. what Im basically trying to do is get so I dont have to load it everytime i reboot. Any one know where to enter the line to get to do so.

Open a console window (clam shell icon on taskbar) and use crontab -e to open your crontab for additions. Put a line like this in the file:

Code:

*/15 * * * * cd /path/to/setiathome; ./setiathome -nice 19 > /dev/null 2> /dev/null

This would attempt to start the seti client every 15 minutes after you login to your desktop or console if it is already running then the command is ignored. To edit the file use the INSERT KEY and

Edit: The line above should be on one line it is ok if it wraps to the next line when editing but there should be no enter key used to have another line in the file. And while I'm at it I should tell you how to edit the file use the INSERT key to enter edit mode then either cut'n'paste the line above and modify to your location or type it in when done hit the ESC key to exit edit mode then the SHIFT and ; keys at the same time to enter command mode then type wq and enter to write and quit the file and it will now be used to start the client new time the crontab is checked for commands to run.

**windos_no_thanks** · 01-20-2004, 12:43 PM

Making newbies use vi seems like unnecessary cruelty these days.

If you say:

Code:

export EDITOR=emacs

before

Code:

crontab -e

You will get a GUI editor which behaves a lot more like the M$ stuff most people are used to yet is still more powerful than vi. (emacs is also much more bloated than vi or vim but that's another issue

)
Another thing: The crontab file MUST end with a newline, otherwise the last line (in this case the only one) will not be executed.

**hmiller68** · 01-21-2004, 01:13 AM

Well first there is no clam shell nor even a task bar in
Blackbox(its a slit).

Hate kde ,too much like winders for me. Thanks for the instrustions for vi even though I prefer nano or joe
.And Im not a newbie I just came from Gentoo and got to used to the rc scripting and the rc-update add feature that I totally forgot about cronjobs. I just wish I could get it to run once and done on boot rather than have the cronjob in there . Plus if I remember corretly cronjobs must be entered for ever user correct?

**Stephen** · 01-21-2004, 03:31 AM

Originally Posted by hmiller68

Well first there is no clam shell nor even a task bar in
Blackbox(its a slit).

Hate kde ,too much like winders for me. Thanks for the instrustions for vi even though I prefer nano or joe
.And Im not a newbie I just came from Gentoo and got to used to the rc scripting and the rc-update add feature that I totally forgot about cronjobs. I just wish I could get it to run once and done on boot rather than have the cronjob in there . Plus if I remember corretly cronjobs must be entered for ever user correct?

You are correct for individual crontab's but if you put the line in the /etc/crontab it would be checked at whatever interval you choose or if you were to make a script and put it in the /etc/cron.daily directory it should be run when the rest of them are. Alternatively you could create a script make it executable then in the /etc/rc5.d directory ln /path/to/seti/script.sh S98setistart -sfn to make a link to start the script near the end of the boot into run level 5 (the default boot level) if you have modified the inittab to start at a different level then make the link in the proper directory.

**arkaine23** · 01-23-2004, 01:43 AM

The customization Overclockix has several seti scripts kept in /usr/local/bin. One of them can be used as an init script, though the iso's are currently using a folding@home init script to fold at startup instead of crunch....

You're welcome to take a peak and critique the scripts- I don't use seti personally so my scripting for it may not be quite perfect.

As it stands now run the commands-

foldon
cfgseti

and you'll be able to login to your seti userid and start crunching.

you can get the scripts only at this Link

Note- The technomancer release is a abit more developed than the Eidolon release, its newer.

**hmiller68** · 01-30-2004, 01:10 AM

Just downloaded andd installedd the technomancer version
to hd everything works great even DRI on the Radeon 7000
Thankss forr the tip for overclockix .

**arkaine23** · 01-30-2004, 01:25 AM

Glad you like it. Its the first of many remastered CD's I have planned. I'll be offering the scripts I use for DC clients to the whole Knoppix community in hopes that these programs can make it into many custom live CD's.

For now though, I'll probably take a few of my favorite Knoppix remasters and re-remaster them just to add folding, seti, and prime... and maybe firebird and mplayer while I'm at it...

One thing to watch out for-

You might want to comment out some lines in /etc/crontab
There are some entries in the system's crontab to stop and start folding@home every 12 hours. Seti should overpower folding in prioity, but I wouldn't want you to lose any cpu cycles to an alternate DC project.