Questions and Answers :
Unix/Linux :
Spawning Seti
Message board moderation
Author | Message |
---|---|
JTKirk Send message Joined: 13 Jun 99 Posts: 6 Credit: 2,526,879 RAC: 0 ![]() |
I had to do some work on my machine and went to kill the seti process, which I did, checked top, it was still there, did it again, and again, and again; eventually decided that it seemed to be starting new processes every time I killed one. I had to reboot to clear things up. Any idea what causes this and if there is a way to prevent it in the future? |
Martin Porstner Send message Joined: 30 Sep 99 Posts: 2 Credit: 1,541,507 RAC: 0 ![]() |
I think you would have to either - only stop the seti process "kill -STOP " or similar) and later resume it with "kill -CONT " or - kill the boinc process that controls and restarts seti. |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
before killing the seti proccess you have to kill the boinc proccess. if you only killed seti then boinc will restart a new setiathome proccess and that´s what happend on your machine. ;) you could use something like: ----- #! /bin/sh cd /opt/boinc/ kill `ps aux | grep setia | grep -v grep | awk '{print $2}'` kill `ps aux | grep boinc | grep -v grep | awk '{print $2}'` #! /bin/sh rm /opt/boinc/lockfile ------ for stopping and ------ #!/bin/sh cd /opt/boinc /opt/boinc/boinc_client -return_results_immediately > /dev/tty10 3> /dev/tty10& ---- for starting the proccess Regards Crunch3r ![]() Join BOINC United now! |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.