When newly attaching a host to a project, it may happen that it gets a resource share of "0" instead of "-" when checking the host details out. This leads to warning messages in the client: "Resource share out of range: 0.000000".

TIA

Resource share 0 is now allowed since the latest BOINC client (should) support(s) this as "only fetch work when no other attached project has work (per request of this thread)

That's interesting, but the newly attached project has a default share of 100. Why do you think that it should default to 0 when the project default is something else?

TIA

ah, now I understand. I'll have a look

So I attached a new host to BAM! and all resource shares were taken from default, nothing zeroed out. When I add a new project to the host, the resource share is again the default, not zero.

So probably I still do not understand you correctly. Please try to explain again.

The problem I have is even getting a Project to set to 0 using BAM. I did yesterday at the Collatz Project, it set the Project to 0 Resource Share but some hours later when I checked Collatz was at 100 Resource Share again & I haven't been able to get it to 0 again no matter what I do.

Willy,

Please, see this host. I just added Malaria to it and, as you can see, its resource share is 0, not the default "-". Note that FreeHAL has sported a resource share of 0 since I attached the host to it.

TIA

i did not think it was the same problem, so i started a new thread - if you do not want any help in finding the bugs - go figure yourself.

Not sure if this is related, but .... on the account with BAM ID = 76666 there is this host that apparently uses no resources on any project ...




even though the assigned project resource shares would say otherwise ...

Changed this.

When a project is set to attach with the previous status being not-attached, the resource share is set to '-'.