It would be nice to have a user friendly interface to create and or change all configuration files so the user does not have to guess on what parameters need to be included in the file.

---

The user doesn't have to guess, if he uses the documentation at http://boinc.berkeley.edu/wiki/Client_configuration

---

The request is for a user friendly interface to create and or change all configuration files. The documentation that you refer to is not user friendly for the non-techie.

BOINC out of the box should do everything as is, without the need to add any configuration files. These configuration files are only necessary for e.g. giving debug info back, or to fine tune parts of the working of BOINC or a project's application. But then you need to have some understanding of BOINC already, be at a level above a novice, have some understanding of what does what and why it does that.

Added to that, I asked the developers a while ago about adding an option to reread the app_config.xml file, whereupon they answered me that a) this file is only here temporarily, it'll go away again in the future; and b) that they're not going to add anything to the present graphical user interface.

The solution to my request was to piggy-back the reread of the app_config.xml file on the existing Read config file option already in the menu.

Do know that when you add an exclusive application through the present advanced preferences menu, that BOINC then writes a cc_config.xml file with all log flags and options in their default settings in the data directory. Which should help you along, when you put that next to the documentation.

---

Not sure about your second para... since 7.0.54 the app_config.xml is read in via the general Read Config on the Advanced menu, to facilitate instant application [you posted the changelog with the note]. I've tested it wit <max_concurrent> changing from 7 to 6 to 7 and sure enough, going to 6 one task was preempted and restarted after changing value to 7 and reading config again.

Crunch on.

BTW, Get BOINCTasks and you have yourself a full cc_config.xml edit screen, in GUI. Who's still using the standard BM ;?

P.S. Working the cloud via backdoors with a strong argument ;>)

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

The reason this was asked for was to give the end user more control over how many tasks can be run on an individual GPU and or to be able to exclude a GPU from running tasks in a multi GPU environment. The only way that I know of having this much control over BONIC on a machine is to use the config file was for someone that is not tech savvy is very cumbersome.