• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

-Local question

Jon855

[H]ard DCOTM January 2008
2FA
Joined
Aug 25, 2005
Messages
12,132
I have one little question about the -local flags

I have my clients in their own folders, would I still need to use the -local and what exactly does this do?

Thanks.
 
Taken from here: http://folding.stanford.edu/console-userguide.html

-local
Use configuration files from local directory. This option has no meaning on Linux, but is vital on Windows and Macintosh for running multiple clients on a machine. It instructs the client to read its config information from the client.cfg file in the current directory rather than, on Windows, from the installation directory specified in the registry, or, on Macintosh, the Library/Folding@home directory. Information such as the user name, team name, proxy information, machine ID are maintained in the client.cfg file. The flag ensures that work does not conflict. Use "-local" only if you are planning on running more than one instance of Folding@Home on the same machine (this is only useful if you are running on a multi-processor machine). Create as many directories as there are processors on the machine, copy the exe files and client.cfg file into each of these directories, run "FAH3Console -local -config" on each and specify unique machine IDs for each directory (under the Advanced Settings option). From then onwards you may run each copy by switching to its directory and running with the -local flag.

It's a must for multicore boxen, as you need it to keep configuration information separate and the clients from clashing.

 
I've never used the local flag and I haven't had any problems. Is this only for the older console clients?
 
Maybe this is moot when running as a service since it runs from c:\fah1/c:\fah2 etc. and starts in the respective folder.

I don't run -local on multi CPU installs either.
 
That's what I was wondering as I have it under D:\Folding\Fold1\ and Fold\2 respectfully. No need for -local? I just want to be sure that I'm doing it all right and also each has its own machine id
 
Back
Top