Results 1 to 6 of 6

Thread: Can't get app_config to work.

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Silver Member
    MindCrime's Avatar
    Join Date
    February 26th, 2014
    Location
    Portland, OR
    Posts
    967

    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

  2. #2
    Administrator
    Bryan's Avatar
    Join Date
    October 27th, 2010
    Location
    CO summer, TX winter
    Posts
    6,457

    Re: Can't get app_config to work.

    Quote Originally Posted by MindCrime View Post
    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.


  3. #3
    Administrator
    STMahlberg's Avatar
    Join Date
    November 1st, 2010
    Location
    AREA 51
    Posts
    1,533

    Re: Can't get app_config to work.

    Quote Originally Posted by MindCrime View Post
    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.
    Last edited by STMahlberg; 02-17-17 at 05:35 AM.
    "My god! Do we really suck, or is this guy really that good?" - Mr Hertz - Shoot 'Em Up






Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •