Is the Battery preference ever going to get fixed for venues other than the default one?

It was broken on 5.11, and is still broken with 6.01.

Alinator

Works for me in 5.10.20/Vista.

I used BOINC Alpha to change the host location to school. I set Do work while on batteries to NO. I cleared my local prefs. I made sure the activity menu was set to run based on preferences. And I updated BOINC Alpha to pull down the new preferences. I switched off my power converter (easiest way to put the computer on battery power). Everything changed to suspended -- on battery.

I went back to BOINC Alpha and changed my battery prefs to YES for the school venue. Updated. Turned off the power converter again. BOINC went on happily crunching.


So make sure you don't have a global_prefs_override file hanging around. Make sure the host is actually set to the location you think it is. Make sure the activity menu is set to run based on prefs. The usual troubleshooting stuff.



PS: You really shouldn't be using 6.1 either. Rom has asked people to roll back to the latest stable.

---

Kathryn :o)

Make sure your activity menu is set to "Run based on preferences" and not "Run always".

EDIT: But Kathryn already said that. Note to self: wait one or two hours between waking up and replying posts on forums.

No, I am not talking about whether or not the CC's will execute the battery preference correctly or not, they do.

I'm talking about the website preference interface on server builds 5.11 and 6.01.

1.) All venues except the default will show the preference as 'No' regardless of whether you have set it to 'Yes'.

2.) If you have more than one extra venue set, if you change the preference on one of them to 'Yes', it will change it internally and relay it to the host on the next update. However, all the other named ones get reset to 'No'. In addition if you have set one of the named venues to work correctly (despite it showing otherwise), any change to any other pref on any venue ends up having the battery pref for the named venues reset to 'No'.

<edit> Looking back in my logbook, SB 5.09 worked correctly. I explicitly tested this when I noticed my notebook's battery get sacked quickly a couple of times when I knew for fact my prefs should have suspended work on batteries.

Since I routinely use SAH as my primary control project, I noticed they had upgraded to 5.11. I tried using EAH (which was still on 5.09 at the time) and it worked correctly, so I've using it as the primary since then. The other day my notebook battery got sacked again unexpectedly, so I checked and sure enough EAH had upgraded to 6.01, which is how I found the battery pref is still broken on more current versions.

Alinator

1.) All venues except the default will show the preference as 'No' regardless of whether you have set it to 'Yes'.

2.) If you have more than one extra venue set, if you change the preference on one of them to 'Yes', it will change it internally and relay it to the host on the next update. However, all the other named ones get reset to 'No'. In addition if you have set one of the named venues to work correctly (despite it showing otherwise), any change to any other pref on any venue ends up having the battery pref for the named venues reset to 'No'.

I don't own a laptop and I don't want to mess up with venues, so I can't test this myself. I'll post on the mailing lists pointing to this forum thread. Rytis (the maintainer of the web parts) isn't online right now, so you'll have to wait at least till tomorrow for a definite answer.

1.) All venues except the default will show the preference as 'No' regardless of whether you have set it to 'Yes'.

2.) If you have more than one extra venue set, if you change the preference on one of them to 'Yes', it will change it internally and relay it to the host on the next update. However, all the other named ones get reset to 'No'. In addition if you have set one of the named venues to work correctly (despite it showing otherwise), any change to any other pref on any venue ends up having the battery pref for the named venues reset to 'No'.

I don't own a laptop and I don't want to mess up with venues, so I can't test this myself. I'll post on the mailing lists pointing to this forum thread. Rytis (the maintainer of the web parts) isn't online right now, so you'll have to wait at least till tomorrow for a definite answer.

LOL...

Given what I've been seeing here, I can't say I blame you for that! ;-)

Anyway thanks for spreading the word around on the mail lists, and the tests are easily duplicated and repeatable.

Also, just to make sure I read your previous post on the versioning correctly;

You're saying that the server part of a build will report itself in the CC message log as being whatever the version of the client portion was for the tarball it was built from, even if the server part was actually older (or newer) than that?

Alinator

Also, just to make sure I read your previous post on the versioning correctly;

You're saying that the server part of a build will report itself in the CC message log as being whatever the version of the client portion was for the tarball it was built from,

Correct there.

even if the server part was actually older than that?

Not really; the server part doesn't officially have a version number, so you can't compare the version numbers ("older than that") :) Given how fast the server changes, the SVN revision works pretty well as a server version number.

Also, just to make sure I read your previous post on the versioning correctly;

You're saying that the server part of a build will report itself in the CC message log as being whatever the version of the client portion was for the tarball it was built from,

Correct there.

even if the server part was actually older than that?

Not really; the server part doesn't officially have a version number, so you can't compare the version numbers ("older than that") :) Given how fast the server changes, the SVN revision works pretty well as a server version number.

OK... Sheesh, that's a fine how do you do. Why report anything at all (to the CC's) in that case! ;-)

I posted on the SAH and EAH NC fora to see if I can get the SVN rev # to post here and narrow things down a bit.

Alinator

Addendum:

It came to my attention the 'Run with When User is Active' global pref has the same issue.

Alinator