[subego]

How the bleepity-bleep do you stop the CLI client?

I've looked high and low for this somewhat important bit of information. Can I just close out the window without munging my current work unit?

[reader50]

If you have it's window open, Cntrl-. or Cntrl-c or Cntrl-x

If it's in the background with the window closed, then kill it. It does a checkpoint every 10-15 minutes, killing it will cause it to lose only the work done since the last checkpoint.

You can use Activity Monitor to find the process and kill it. Or use 'top' in Terminal to find it's PID, then issue a 'kill 123' in Terminal, where 123 is Folding's PID.

[subego]

Awesome!

[Welnic]

Just to note that the process you want to kill is the CLI client itself, not the core that actually does the work. This is whatever you ran to start folding. I've renamed my client fah6, so if I run:

killall fah6

in the terminal then that shuts down all of my clients. Done this way the client shuts down gracefully, telling the core process, which is called something like FahCore_78, to shutdown. If you kill the core process then the next time the client runs it will run in safe mode since the last time the core died unexpectedly.

[reader50]

Welnic is correct. Folding checks to see if it shut down gracefully the last time, and disables AltiVec / SSE if it detects an unexpected shutdown.

If you launch with the -forceasm flag, this previous-shutdown-check is bypassed, and optimizations are forced on.

[subego]

Originally Posted by Welnic 

that shuts down all of my clients

Can I infer from this that if I have more than one processor, I should be running multiple instances of the client?

I have a dualie G4.

[Welnic]

Yes, that is correct. There is a version that uses more than one processor but it only runs on Intel rigs. You need to have another folder for it to run in, and then copy just the client into that folder. When you are setting it up you need to say yes when asked about advanced configurations, and then change the machine id from 1 to 2 when that question comes up. You also need to run it with a -local flag. The instance that you already running puts its files in a folder in your Library, if you run a second version without using the -local flag it will try to use that folder also. The -local flag means that it will put everything in the folder it runs in. To do this you either need to just add -local when you run the client, or make a little script to start it. You can just start it like:

./fah6 -local

Or write a little script. Just use the text editor and enter the following line:

nohup ./fah6 -local -advmethods &

nohup means that the client will not quit if you log-off. The fah6 is whatever your client is actually called. The local flag makes it run in the directory that it is in, advmethods makes sure that it always uses the advanced processor methods, on a G4 that means AltiVec. The ampersand at the end means that it will run in the background. This means that once this starts running control of the terminal will return. If you want to see what is going on then you need to look at the FAHlog.txt file.

After you enter that line then save the file in the new folding directory. You do not want to have any extensions on the file, if it has .txt or .rtf then remove that. Then run:

chmod +x foldit

if foldit is the name, and that will make it so that it will run.

Then you need to run it once the normal way, to set up the configuration. Just start it like:

./fah6 -local

and then answer the questions. Wait to see if it starts working correctly. Then hit Command-., and restart it with:

./foldit

Then you can run:

tail -f FAHlog.txt and that will give updates whenever something happens.

[subego]

Thank you!