Folding: "-local" flag setting

MGP · 14 Oct 2006 at 19:24

Slightly confused as I'm trying to assimilate a multicore CPU

In Billy with a pointy thing's big sticky it says:

BillytheImpaler said:
Setup for Dual Core, P4 HT, and Multi Processor machines

The setup is exactly the same as for a single CPU except for a few things.

Put another copy of the console in a *different* directory. Otherwise they’ll interfere with each other. I like to put one in C:\Fold1 and another in C:\Fold2. You do the same things as with a single client; same with the shortcut, same with the registry edits. It's just that you have to do each twice. Using the -local flag in this instance is especially important

I might need a trip to specsavers, but I can't see where I need to use this flag :confused:

diogenese · 14 Oct 2006 at 19:44

straight from the horses mouth, here

-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.

MGP · 14 Oct 2006 at 19:55

But how does that fit in when you set it up as a windoze service cos I need to do that on borgs.

oceaness · 14 Oct 2006 at 20:02

From the Billy's sticky

Performing the registry edits

Think thats what you want?

MGP · 14 Oct 2006 at 20:05

I've followed the registry edits in that sticky. but they don't mention the -local flag. Should they go into the same registry bit, or somewhere else?

oceaness · 14 Oct 2006 at 22:39

yeah same place I think.

SiriusB · 14 Oct 2006 at 22:52

Who says you need the local flag? I never set it and to be honest I really don't see why you would.

SiriusB

MGP · 15 Oct 2006 at 00:11

If it's not needed, then why mention it :confused:

oceaness · 15 Oct 2006 at 00:19

As posted by diogenese.

It's useful when running more than one instance. Thought I'm not sure it's relevant unless you use the installer/GUI version. I set it just incase. I think it has been known to cause problems by running exactly the same WU twice, once on each core at the same time and obviously it gets confused.

A.N.Other · 15 Oct 2006 at 00:32

I don't believe that it's needed any more - it was only for older versions of the client. Some guy on the F@H forums read Billy's guide and pointed that out there.

SiriusB · 15 Oct 2006 at 02:19

I thought it was a bit redundant. I mean when you create two separate folders and run the clients from within them, that's it they live in those separate folders and there is not a chance in hell they could get confused and accidently modify a different client's cfg file.

Makes me wonder if they have ever needed the local flag to be honest...

SiriusB

MGP · 15 Oct 2006 at 10:14

I'll stop worrying about it now thanks.