Can't get app_config to work.
<app_config>
<app>
<name>SixTrack 451.07 (pni)</name>
<max_concurrent>6</max_concurrent>
</app>]
</app_config>
The app_config.xml file was place in the following directory where all the SixTrack programs are located. C:\ProgramData\BOINC\projects\lhcathome.cern.ch_lh cathome
I took the app name from the properties below. This was the first one I tried and I have tried all of the following as well:
451.07 SixTrack (pni)
451.07 SixTrack
SixTrack 451.07
SixTrack
None of them work... it still runs 7 wu's instead of 6. I'm at a lose.
Computer: Aurora
Project LHC@home
Name w-c0_lhc2016_40_MD-185-16-476-2.5-0.9878__49__s__64.31_59.32__7_8__6__85.5_1_sixvf_b oinc55211_1
Application SixTrack 451.07 (pni)
Workunit name w-c0_lhc2016_40_MD-185-16-476-2.5-0.9878__49__s__64.31_59.32__7_8__6__85.5_1_sixvf_b oinc55211
State Running
Received 2/14/2017 7:45:00 AM
Report deadline 2/20/2017 11:17:16 PM
Estimated app speed 23.84 GFLOPs/sec
Estimated task size 180,000 GFLOPs
CPU time at last checkpoint 00:07:02
CPU time 00:07:19
Elapsed time 00:07:43
Estimated time remaining 01:53:39
Fraction done 9.681%
Virtual memory size 77.07 MB
Working set size 59.27 MB
Directory slots/20
Process ID 3908
Re: Can't get app_config to work.
try plain sixtrack, without the stray ] char in it. After reloading config files, see what your log/messages say. The project says no available anyway though....
<app_config>
<app>
<name>sixtrack</name>
<max_concurrent>6</max_concurrent>
</app>
</app_config>
Re: Can't get app_config to work.
Quote:
Originally Posted by
scole of TSBT
try plain sixtrack, without the stray ] char in it. After reloading config files, see what your log/messages say. The project says no available anyway though....
<app_config>
<app>
<name>sixtrack</name>
<max_concurrent>6</max_concurrent>
</app>
</app_config>
Thanks, that worked. :)
Funny thing, I got a notification about that stray ] and I couldn't see the thing... finally found it.
Re: Can't get app_config to work.
Depending on if the machine has run the application before you can type anything inbetween <name>XXX</name> and when you read configs the event log should tell you the known app names.
Also if you're just trying to limit the project and not the specific app you can do this:
<app_config>
<project_max_conurrent>X</project_max_concurrent>
</app_config>
And thats the whole file no names needed
<project_max_concurrent> was introduced in BOINC 7.4.9
Re: Can't get app_config to work.
Quote:
Originally Posted by
MindCrime
Depending on if the machine has run the application before you can type anything inbetween <name>XXX</name> and when you read configs the event log should tell you the known app names.
Also if you're just trying to limit the project and not the specific app you can do this:
<app_config>
<project_max_conurrent>
X</project_max_concurrent>
</app_config>
And thats the whole file no names needed
<project_max_concurrent> was introduced in BOINC 7.4.9
Depending on which version of Mint you installed this may or may not work. Mint 18 and you are good to go. If you installed anything prior to 18 then the repository gives you BOINC 7.4.22. If that is the case you need to upgrade to at least 7.4.25 and then the project_max_concurrent command works.
Re: Can't get app_config to work.
Quote:
Originally Posted by
MindCrime
Depending on if the machine has run the application before you can type anything inbetween <name>XXX</name> and when you read configs the event log should tell you the known app names.
Also if you're just trying to limit the project and not the specific app you can do this:
<app_config>
<project_max_conurrent>
X</project_max_concurrent>
</app_config>
And thats the whole file no names needed
<project_max_concurrent> was introduced in BOINC 7.4.9
Some of the projects that I've started running recently have bogged down my systems such as LHC, and Primerows. So I've placed app-config files into those projects to keep 1 or 2 cores free.
