Not that I use it much anymore since all my GPUs are the same.

However tonight I was looking to test something and went to open up my cc_config which usually has just the line about using all GPUs.

What I got instead was a laundry list of options and other information which I believe came with the newest version of Boinc.

I'm curious to know if anyone who does use different model GPUs and had been using the "Use all GPUs" in their cc_config noticed this before now and how they worked around it.

Just something for a Sunday evening to think about.

Zalster

I used one of the rare outages that we had to run my cache down to zero and uninstall Lunatics, remove SETI@Home and uninstall BOINC 7.4.42, but before I did that I saved a copy of cc_config.xml to my Desktop because I was too lazy to copy/paste that again.

I removed the BOINC folder and installed 7.6.2. Before I added a project I copied my cc_config.xml back; I don't remember there being an existing cc_config.xml in there. I only need the file because there's a bug in the newer ATI drivers that makes the first card OpenCL 2.0 and subsequent cards OpenCL 1.2 so BOINC thinks the first card is superior when they're really identical.

So my cc_config.xml doesn't have any new stuff in it.

There have not been many additions to the cc_config.xml recently. When a new item is added the version where it first appeared is noted at the end of the entry.

However what has changed in there is now a GUI interface in BOINC manager to enabled or disabled the options. I would imagine if you use the GUI. That it writes all values to the file instead of just the items you select/change.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I don't use the iGPU on my machines. But I think what might have happen is I did select an option on the advance bug notifications a while back. I'm thinking maybe that caused the file to be written in. I bet if I reloaded BOINC that it would delete that file but since I don't really use it, I'm not going to worry about it too much. I was only concern in case others run mixed GPU units that it might interfere with the settings.

Thanks


Zalster

... which I believe came with the newest version of Boinc.

No, it didn't "come with" BOINC, it's "written by" BOINC any time you change any setting by using the Manager GUI.

The difference is that whenever BOINC writes out the file, it fills in all the current settings, including any you might have set manually (and default values for the rest).

It does write all values, so the the one you want is in there somewhere. They're in alphabetical order, so "Use..." is way down the bottom. The only danger (which has happened) is that someone takes a cursory glance, doesn't see what they're looking for, and adds it back in manually. If you get duplicate entries like that, it's the last one read (lowest down in the file) which gets acted on, and that probably isn't the one you added manually.

... which I believe came with the newest version of Boinc.

No, it didn't "come with" BOINC, it's "written by" BOINC any time you change any setting by using the Manager GUI.

The difference is that whenever BOINC writes out the file, it fills in all the current settings, including any you might have set manually (and default values for the rest).

It does write all values, so the the one you want is in there somewhere. They're in alphabetical order, so "Use..." is way down the bottom. The only danger (which has happened) is that someone takes a cursory glance, doesn't see what they're looking for, and adds it back in manually. If you get duplicate entries like that, it's the last one read (lowest down in the file) which gets acted on, and that probably isn't the one you added manually.

Not quite in alphabetical order. Only within each section, of which there appears to be at least 4. So it is a real PITA to check (7.4.42)

---

... which I believe came with the newest version of Boinc.

No, it didn't "come with" BOINC, it's "written by" BOINC any time you change any setting by using the Manager GUI.

The difference is that whenever BOINC writes out the file, it fills in all the current settings, including any you might have set manually (and default values for the rest).

It does write all values, so the the one you want is in there somewhere. They're in alphabetical order, so "Use..." is way down the bottom. The only danger (which has happened) is that someone takes a cursory glance, doesn't see what they're looking for, and adds it back in manually. If you get duplicate entries like that, it's the last one read (lowest down in the file) which gets acted on, and that probably isn't the one you added manually.

Not quite in alphabetical order. Only within each section, of which there appears to be at least 4. So it is a real PITA to check (7.4.42)

Only two sections:

* Logging flags
* Options

like the documentation. The problem is that 'P' for proxy options has a multi-line entry, and the indenting isn't consistent - you're not the first to be caught out by that.

BOINCtasks also has the ability to edit the cc_config (even of a remote machine) and the end result will be a file with all the tags even though you may only have changed one of them.

Personally I prefer to edit the thing by hand so you don't get all the tags.

---

BOINC blog

Adding a program through the Exclusive CPU applications option in Computing preferences... in all of the BOINC 7 versions will add all of the options section into the cc_config.xml file, plus of course the excluded program.

It was easier to have it add all of the options, than to try to only add the exclusive_app tags and make a jumble of the contents of the file (e.g. by adding onto it all the time). Now it follows a template, rewriting all of the file each time something changes through the GUI, with all that wasn't set before set in its default value or form.

With BOINC 7.4, the Event Log Diagnostics window adds the log flags section as well.
With BOINC 7.6, Exclusive GPU Applications can be set through the GUI as well.

---