what would happen if...

[alpha754293]

what would happen if you were to manually edit the client.cfg file such that the Machine ID is > 16?

[uncle_fungus]

The client will reject the Machine ID and reset it to 1.

[alpha754293]

Hmm. ok. thanks.

[uncle_fungus]

On Linux machines the point is moot, since each client generally has it's own userid so machineids tend to matter less. The userid is stored in machineindependent.dat the working directory if this is missing the client will just ask for a new userid.

On windows the userid is stored in the registry, so all clients get the same userid and then add the machineid to it.

[alpha754293]

Well...I'm just asking to try and figure out how many F@H clients I can support with larger systems per OS installation/instance. (i.e. > 32 cores) From what I can tell right now, with 16 machine IDs, I can run upto about 64-cores if I use "-smp 4" (more uniform support) in a single OS installation, or upto 128-cores if I go with "-smp 8" (in which case, potentially half of the cores would be unused if by some freak of nature, that all 16 clients are running a1 cores.)

[uncle_fungus]

On Linux it's unlimited because each client can have a unique userid. On Windows, under normal circumstances you can only run 16 clients.

[alpha754293]

I've ran into issues even in Linux before where it said that it couldn't run the client because of a machine ID conflict. I would have to verify that, but I'm pretty sure of it.

[7im]

Not unless you copied the machineindependent.dat from one client to another on linux. That error is typically a Windows only message about ID conflicts.

[alpha754293]

Not unless you copied the machineindependent.dat from one client to another on linux. That error is typically a Windows only message about ID conflicts.

Ahhh...that might be why I got that error then. I think that I came across it when I was doing the benchmarking because I was replicating the same WU (the entire fah client directory) repeatedly.

Got it. Thanks.