where to set no# CPU's in preferences

Hello,

Installed the latest boinc on a Linux box, 2.6 kernel, which has two CPU's and yet somewhere, when running the client, it is being limited to using only one CPU. My preferences in the Seti account shows that any computer can use up to 4 CPU's. I have another Linux computer and it is using 4 CPU's. Can't seem to find a local file restricting the use to only one processor.

Any help on how to resolve this would be greatly appreciated.

Thank you,

JP

It's in your Computing preferences:

Thank you for your response. I have it set to use 100% of the processors. What is interesting is one computer is using all 4 processors while the other, using the identical preferences, is only using 1 CPU.

Thank you again,

JP

Did you check online and local preferences?

Gruß,
Gundolf

I don't see an option for number of processors in the local preferences, only processor usage.

JP


____________

For BOINC 6, it's called On multiprocessors, use at most xxx% of the processors, both in the web preferences and in the local advanced preferences (BOINC Manager->Advanced view->Advanced->Preferences->Processor usage)
____________
Jord

- BOINC FAQ Service
- BOINC User Wiki

Real is just a matter of perception.

There should be one option to set percentage of processors and one to set percentage of processing (CPU) time. I can't tell the exact wording, because I'm still running BOINC 5.10.45, but both should be at 100%.

Do you have a cc_config.xml file in your BOINC data directory (where the client_config.xml resides)? If so, check the <ncpus> option.

Gruß,
Gundolf

It appears that problem lies with Seti using the online defaults preferences and not the home preferences. Any way to force it to use home?

Computer location: home
General prefs: no separate prefs for home; using your defaults.

I created a work prefs and assigned the computer to it, yet Seti still loads from the default prefs.

Thanks again,

JP

Thanks everyone. At the bottom of the Advanced Options page were the CPU settings. The page wasn't fully expanded and I only saw after resizing the window.

JP