• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Seti on K6-2+ running Mandrake Linux 8.2

sduguid

Senior member
I have a couple of quick questions somebody can hopefully help me with.

I have an older system which runs Win98 and I have set it up to dual boot with that and Mandrake Linux 8.2. I anticipate that it will run Linux almost full time from this point on. It's an old DFI Pentium mainboard which I've upgraded with a K6-2+ 450. The maximum the board will do is 75mhz bus speed but in Windows I can use a utility to change the multiplier to 6.0, thus making the processor speed 451mhz. It does a WU in about 24 hours.

I have found a driver to raise the multiplier for the k6+ processors in Linux as well, though I haven't tried it yet - hopefully that will work.

My point is that I'd like to set Seti up to automatically run in the background. I want it to start when Mandrake boots and I'd like it to try to start once an hour in case something has happened and it shuts down. I don't need to see any evidence that it is running - it will be reporting to Maxsiren's proxy about once a day if it is running properly. So, does anybody know anything about CRON jobs?? Any help would be appreciated. I may not get around to doing it for a couple of days so I'm in no big rush.

Thanks 😀
 
Step aside, I'll handle this !!!!

Just edit a crontab to run it every hour (if it's not already running).
You can do this with any user ID, as long as that user ID has read/write privelidges in the directory you created for Seti.
You could run it as root if you want...


So.

log in as whichever user... I'll call the user col

crontab -e col (opens in edit mode the crontab for user col)
i (goes into insert more)
10 * * * * cd /home/col/seti/setiathome -proxy xxx.xxx.xxx.xxx:xxxx -nice 19 & > /dev/null 2>&1 (tries to start seti in the directory /home/col/seti at 10 past every hour, points it at a proxy server of your choice, runs it at the lowest priority, in the background, sends all messages to the bin)
<esc>
:
wq! (these 3 lines will exit the crontab and save your changes)

should work,

just do a ps -ef | grep -v grep | grep seti to see if it's running

good luck,

Col
 
Hey ColinP.... That's good for keeping it running.


However,....

You also want to set up an entry in /etc/init.d (that's it's home in debian land.... I think it's different in mandrake land, but I'm not sure where), and then set up links
to an appropriate S9* entry in /etc/rc2.d, rc3.d, rc4.d, rc5.d, and then K0* in /etc/rc0.d, rc1.d & rc6.d, to make sure it starts & stops at bootup/shutdown time....

--------------------- script starts here --------------------------------------
#!/bin/sh
# Start/stop the setiathome process

test -f /setiathome/setiathome || exit 0

case "$1" in
start) echo -n "Starting setiathome"
cd /setiathome
exec ./setiathome -nice 19 -proxy 192.168.0.10:5517 > /dev/null 2>&1 &
echo "."
;;
stop) echo -n "Stopping setiathome"
cd /setiathome
kill `cat pid.sah`
echo "."
;;
*) echo "Usage: /etc/init.d/setiathome start|stop"; exit 1
;;
esac
exit 0
----------------------- script ends here -------------------------------

then my startups are:
/etc/rc2.d/S91setiathome
/etc/rc3.d/S91setiathome
/etc/rc4.d/S91setiathome
/etc/rc5.d/S91setiathome

and my kills are:
/etc/rc0.d/K09setiathome
/etc/rc1.d/K09setiathome
/etc/rc6.d/K09setiathome
 
Wow! :Q Thanks for the help 🙂

I won't be able to try it out for a couple of days but I'll let you know how it goes!

😀
 
Originally posted by: soni
I think this &iacute;s question for Poof 😛

Just a little bump

LOL! 😛

Technically, you don't have to start it up with the services. You can add an entry in /etc/init.d/rc.local (or boot.local depending on the distro) that is similar to how you would start it manually BUT just make sure that you put a "&" at the end of the line so that the process forks into the background once it starts up.
 
Back
Top