Configuring several machines via app_config.xml file

Richard de Lhorbe
Richard de Lhorbe
Joined: 15 Dec 05
Posts: 43
Credit: 9258973743
RAC: 774400

AGENTB - this issue was a bit

AGENTB - this issue was a bit different, in that with the cc_config.xml file I could see everything in the directory but wanted to modify one single ile that was locked.   In this case with the app_config.xml file, I could not even see what was in the projects/ directory at all and did not know if that was the right place or not .... I am pretty cautious with messing around with changing things when they are locked, as I don't want to "break the installation" like Christian cautioned.

In this case, I took Gary's suggestion and added myself as a user to the BOINC directory, which then enabled me to easily add the app_config.xml file I wanted to.  Since that file now seems to have had the desired effect, I am planning to remove myself as a user again.   Since I know the file is in there now, I should be able to use the sudo gedit command in the future if I need to modify it ... but if that doesn't work, I can always add myself as a user again if I need to.

Thanks to all for the suggestions.

Jonathan Jeckell
Jonathan Jeckell
Joined: 11 Nov 04
Posts: 114
Credit: 1341945207
RAC: 1

How would one set up an

How would one set up an app_config.xml to produce different settings for two different GPUs?

I have an NVIDIA GTX 960 and an AMD R9 280X.  I want to feed them different numbers of concurrent tasks.  I've modified app_config.xml files on SETI before, but never Einstein, and I've only done it for one GPU, not two different ones.

 

Holmis
Joined: 4 Jan 05
Posts: 1118
Credit: 1055935564
RAC: 0

Jonathan Jeckell wrote:How

Jonathan Jeckell wrote:

How would one set up an app_config.xml to produce different settings for two different GPUs?

I have an NVIDIA GTX 960 and an AMD R9 280X.  I want to feed them different numbers of concurrent tasks.  I've modified app_config.xml files on SETI before, but never Einstein, and I've only done it for one GPU, not two different ones.

 

Start by reading the documentation on app_config.xml.

Then use the second block shown in the example, the one using the <plan_class> option.
So something like this:

<app_config>
   <app_version>
       <app_name>hsgamma_FGRPB1G</app_name>
       <plan_class>FGRPopencl1K-nvidia</plan_class>
       <avg_ncpus>1</avg_ncpus>
       <ngpus>0.5</ngpus>
   </app_version>
</app_config>

The application name for current FGRP GPU work is hsgamma_FGRPB1G
The plan class names to use can be found on the Applications page, ie FGRPopencl1K-nvidia
For multiple plan classes just add another <app_version> ... </app_version> block.

tjloman
tjloman
Joined: 20 Dec 17
Posts: 1
Credit: 204435
RAC: 0

Rather than first messing

Rather than first messing with group or user settings, you can make the new file under Ubuntu with this command:

sudo nano /var/lib/boinc-client/projects/einsteinathome.org/app_config.xml

Nano is a very user friendly text editor, and allows you to easily use the right-click -> paste function, so I prefer it over vi for modifying and creating data sheets. ctrl+o writes (o is for output under UNIX, not open)

So, after you put in your data, the new .xml file still is still owned by you instead of the boinc group. To remedy this, we simply enter the next command:

sudo chown boinc /var/lib/boinc-client/projects/einsteinathome.org/app_config.xml

This will modify the permissions of the file created in the previous command so that the boinc user will be the new owner of that file.

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.