What happened today?

All my hosts, started to download work from all the attached projects, and other projects went into NNW.

Seems that BAM is over ridding the local host preferences.???

Was just going to post the same. Glad it's not just me...

Edit: I was trying to drain Windoze of work before moving over to Linux. I just moved over to Linux and found the same thing there. BAM has overridden my local prefs for NNW and was trying to get WUs from every project I have ever attached to.

got hit 2 - local settings were overridden when hosts contacted BAM!

Same problem! I am NOT amused!!! I hope this will be fixed soon!!!

I have this behaviour at every contact to BAM!, but only with BOINC 5.8.16 never with 5.10.45.

I'm pretty used to it :-) only wanted to add my 2 cents.

Gruß,
Gundolf

AFAIK, that's how it's supposed to work, as one of the purposes of an account manager is to make it easier to manage remote hosts. This would cause problems with a remote host that you don't have frequent access to.

How to issue "No new work" from BAM

The gag is that NNW is set, but BAM! resets it with the second next connect on the host (5.8.16) for me and without interaction for all other posters!

[edit] correction: just this minute BAM! did contact and didn't cancel NNW for the first time since long ago. I will wait 23 hours for the next contact to verify this. [/edit]

All my hosts are 6.4.5 version


Local hosts SHOULD have priority over BAM -


If you don't have access to a remote host and have set NNW from the client - this is an easy fix with BAM - just detach from the project, and reattach.



I had set NNW on several boxes that I was testing some overclock on specific projects - and BLAMMO - got QMC and other projects that work the CPU a bit more and crashed my systems...

I found 1 box running at 106c - almost melted the mother board

First of all: When a host is attached to BAM!, BAM! is in control. If you change settings locally there is a good chance BAM! will override so it's better to use BAM! when both the host and BAM! offer the same feature.

On to the problem: read Host does not obey BAM. That's why I made the change and I knew I was going to get into trouble.

Part of the problem is that the client doesn't send its NNW status back to BAM! so BAM! can't check if the host obeyed the NNW command.

I will revert the changes and think of another solution.

In general I think the local settings, if they exist, should have priority, and only changes should be sent by the server. If that is not possible with BOINC clients, then I maybe a corresponding change of the client could be proposed (e. g. to report back the status) and you could offer a switch for users to select if they want the online status to be sent all the time or not.

Can you let us know when you have reverted back from the changes?

Thanks.

I reverted the changes right after my previous post.

Personally, I disagree. My primary purpose of using a BOINC ACCOUNT MANAGER is to manage my numerous hosts. Don't get me wrong, I love the stats, but I joined for host management. If BAM isn't controlling the host settings, what's the point in having it? If the manager is set up, the local host should obey, and should be checking to be compliant at every synchronization.

I agree with BAM being the master as there is not "local override", like for the preference for example.
There currently is no local setting in the boinc manager for NNW currently. NNW is only a flag and you either can control it with BAM or you have to detach the client and control it via the local boinc manager. At least thats what i would expect and it started working yesterday.

Not a problem now, I have made the appropriate changes - Just a little warning next time would be nice


Can you develop a switch to allow this control to be user selected?


BAM is an awesome product and you should be highly commended for putting it together - but the only thing I have used it for in the past was to attache or detach from the projects. The NNW controls I have done from the local client.

If you are micro-managing your hosts by setting local preferences anyway, I don't see the benefit of using BAM... The only reason I've ever done anything locally is to attach to a project that is not in BAM. In fact, the first time I did this was just this month with ORE, and I've been using BAM for almost 2 years. BAM is very good for "set and forget", and can complicate other management schemes since it does enforce its "master" status with settings within the BOINC client.

First of all I would like to say that I am glad that BAM is there. Thanks for it!

@Noderaser: If somebody would use local settings for all settings for all host all the time then there probably would be for that person little benefit of using an account manager. I generally use BAM for attaching to projects, setting resources and preferences and for team membership, and find it very useful. The experience is that sometimes it takes quite some time to transfer changed settings to the hosts, also when initiating synchronizations from the BOINC managers. For allowing/disallowing (suspending/NNW) projects to run on hosts I usually use local settings that are effective immediately.

For preferences it is possible to have local settings, and there is also an option to erase them. When they exist, they are used, otherwise global settings are used. As mentioned, in my opinion such a scheme would be best (if it can be introduced). Other option could be "last change wins" (if possible) or a switch for the user to select whether global settings should overwrite local ones. If such a switch was introduced I would prefer the default being not to erase the local data.

I've noticed that adding/removing projects and changing resource share is pretty instantaneous with BAM!, however preferences are a different story because they actually come from the projects... If you change them in BAM!, they will be sent to the projects which is where the extra time comes in. Also note that, if you change preferences on a project website and not through BAM!, the most recently changed preferences will be used for all projects.