This is more of "solution report", than a "bug report", because I contacted the BOINC developers, and the problem will be fixed soon.
Below is the email correspondence. The problem dealt with host-specific Resource Share values (from communication with the Account Manager) getting trumped by Project Resource Share values (from communication with the Project).

Basically, the next version of BOINC (7.3.14+) should have a fix for this issue.

Regards,
Jacob Klein


==================================================
On 19-Mar-2014 3:37 PM, Jacob Klein wrote:

David,

I'm seeing a behavior, and I'm having trouble deciding if it's unsupported functionality, or if it's a bug. Can you please answer and help?

- On the BOINCstats BAM! account manager website, for one of the projects (SETI Beta), I have set a host-specific Resource share (to 0 in my case)
- This is a host-specific setting, separate from the "global project" resource share value.
- I tell BOINC to communicate with BAM!, and I see my client Resource Share get updated (RS changes to 0)
- I click Update on the project, and because the project does not have a "Resource Share change" queued up, my client still correctly says 0.
- I then go to the project website, and change the Resource Share, to 2 for instance
- I click Update on the project, and this time, because the project DOES have a "Resource Share change" queued up, my client now says 2.

Shouldn't it have respected my host-specific account manager value of 0? Or is the concept of a host-specific value, unsupported functionality?
For reference, the client sees that the Project is indeed managed by the Account Manager (I cannot click "Remove&quot

Please let me know,
Thanks,
Jacob

PS: For anyone who cares to hear the detailed reason of why I'm even playing with this, it goes like this:

- My setup was: 2 beefy GPUs set to work on GPUGrid, with other projects excluded, alongside 1 tiny GPU that had GPUGrid excluded. Exclusions are all done using <exclude_gpu> config in cc_config.xml
- That third GPU was set to only work Albert/Einstein/SETI/SETIBETA, but because I didn't want CPU tasks from them, and wanted to minimize RPCs, those 4 projects were set to Resource Share (RS) of 1.
- GPUGrid recently ran out of work, and my beefy GPUs were idle, due to my settings.
- So I changed the GPU Exclusions to allow the 2 beefy GPUs to work on the 4 projects, but because I wanted to prefer GPUGrid, I wanted to change the 4 projects RSs to 0.
- But I have a separate host with a tiny GPU that actually works those 4 projects and cannot do GPUGrid, and to minimize RPCs, I wanted to change the 4 projects RSs to 1.
- So I decided to leave the project RSs set to 1, but do an Account Manager host-specific setting of 0, on my main 3-GPU-rig, for the 4 projects.
- But that host-specific setting of 0, is getting trumped, and changing to a 1. Bug, right? Sigh.
- If anyone has a better way to accomplish what I want, without doing venues, I'm listening.

==================================================
Date: Wed, 19 Mar 2014 16:33:32 -0700
From: d...@ssl.berkeley.edu
To: boinc_alph...@ssl.berkeley.edu
Subject: Re: [boinc_alpha] Account Manager Host-specific Resource Share vs. Project Resource Share

It's a bug; if an account manager specifies a resource share,
that's supposed to trump the one returned by projects.

I fixed this (not tested).

-- David

==================================================
From: j...@msn.com
To: d...@ssl.berkeley.edu; boinc_alph...@ssl.berkeley.edu
Subject: RE: [boinc_alpha] Account Manager Host-specific Resource Share vs. Project Resource Share
Date: Wed, 19 Mar 2014 20:06:54 -0400

Thanks for the quick response. I'll try to give it some testing, in the next BOINC alpha release.
Host-specific settings are a handy feature for an Account Manager to have!

==================================================