|
|
Upgrade (not)
I'm running the 3.03 version and aware of their cron suggestion.
Upgrade (not)
Ok, so adjust the cronjob to only launch if setiathome isn't running:
0 * * * * cd setidir; ((ps ax | grep seti | grep -v grep) || ./setiathome -nice 19) > /dev/console 2> /dev/console Check for the presense of the setiathome process, filter out the check itself, and if the check fails then launch seti again. There's probably about a million ways to do this ("timtowtdi"), but as a general rule I still think that ways that work through the cron system are going to be more suitable than ways that try to avoid or work around it. My actual line goes to /dev/console (now, but I may put it back to /dev/null if I decide I'd rather have it run quietly), and more importantly it also sends an email if anything goes wrong (which seems like a better alert mechanism than the console anyway, at least to me -- it can go to another machine, can be read later, etc). |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|