 |
 |
Even with "&" F@H still closes with terminal window
|
 |
|
 |
|
Mac Enthusiast
Join Date: Nov 2003
Location: Boise, ID
Status:
Offline
|
|
So I'm trying to run the Folding @Home client in teh background. Yes, I know I can setup the crontab to get it to start up and run in the background on startup, but on occasion I have to quit the process, and want to be able to run it again when I'm done. Thus far I'm using this command:
./fah4 -local &
however, the process quits when I close the terminal window. Any help?
TIA
-Kris
|
-Kris Olson | 12" PBG4 1.5GHz
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Nov 2003
Location: Minnesota
Status:
Offline
|
|
Originally posted by bimmerphile:
So I'm trying to run the Folding @Home client in teh background. Yes, I know I can setup the crontab to get it to start up and run in the background on startup, but on occasion I have to quit the process, and want to be able to run it again when I'm done. Thus far I'm using this command:
./fah4 -local &
however, the process quits when I close the terminal window. Any help?
TIA
-Kris
use the following, instead:
/usr/bin/nohup /Applications/fah4 -local -advmethods -forceasm &
nohup will keep it running when the terminal window closes. The other flags are just good to have to make sure that fah doesn't disable its optimizations.
|
|
|
| |
|
|
|
 |
|
 |
|
Forum Regular
Join Date: Nov 2002
Location: Santa Barbara CA
Status:
Offline
|
|
I just make a little script that calls the client:
#!/bin/sh
./folding -advmethods -local -forceasm >/dev/null &
I have renamed the F@H client folding. You can just call the script and then not worry about it. I also call the script with cron when it starts up. That way any changes that I need to do with the script apply everytime I run the client.
I call the script foldit so a simple:
./foldit
starts the client running and it doesn't quit when you close the terminal. The >/dev/null keeps the output from constantly printing to the terminal. If I want to keep track of what it is doing I run:
tail -f FAHlog.txt
which prints out the last 10 lines of the log and then prints any new lines as they are added.
|
|
|
| |
|
|
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Jun 2003
Location: NY
Status:
Offline
|
|
>/dev/null
Can I redirect it to go the the Console log instead?
|
|
|
| |
|
|
|
 |
|
 |
|
Forum Regular
Join Date: Nov 2002
Location: Santa Barbara CA
Status:
Offline
|
|
Originally posted by SciFrog:
>/dev/null
Can I redirect it to go the the Console log instead?
I think that you could do that. You would want to use ">>" which basically appends instead of replacing. Using ">" would replace the log with just the FAH output. I'm not sure that you would have the permissions to do that anyway to the Console log.
You could also use the Console to open the FAHlog.txt file.
|
|
|
| |
|
|
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Jun 2003
Location: NY
Status:
Offline
|
|
So how do you get some units stacked up if you have no internet connection?
|
|
|
| |
|
|
|
 |
|
 |
|
Administrator 
Join Date: May 2000
Location: California
Status:
Offline
|
|
Originally posted by SciFrog:
So how do you get some units stacked up if you have no internet connection?
If the machine truly has no internet connection, sneakernetting the client folder back and forth would work, but would get very tedious. The folder would have to be moved to another machine of the same type because file formats vary slightly between platforms.
If you have dialup, you can cache a few units by running more than one install of Folding. Assuming your machine is fast enough to complete the work in time with (for example) 3 instances running, you are effectively cacheing an extra couple of work units.
|
|
|
| |
|
|
|
 |
 |
|
 |
|
|
|
|
|

|
|
 |
Forum Rules
|
 |
 |
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
 |
 |
 |
 |
|
 |
|