BOINC 5.2.5 is now available for Windows and Linux.
Download and version details from http://boinc.berkeley.edu/download.php

kewl

---

http://boinc-doc.net/boinc-wiki/index.php?title=Aborting_CPU_benchmarks%2C_one_or_more_active_tasks_are_still_running

Is this discusting prob fixed in the new version?

---

http://boinc-doc.net/boinc-wiki/index.php?title=Aborting_CPU_benchmarks%2C_one_or_more_active_tasks_are_still_running

Is this discusting prob fixed in the new version?

It is supposed to be. The same delay as is in the 4.45b version is supposed to be standard now.

---

BOINC WIKI

BOINCing since 2002/12/8

Version 5.2.6 (Windows/Linux) is now available from http://boinc.berkeley.edu/download.php

It is supposed to be. The same delay as is in the 4.45b version is supposed to be standard now.

No. No. The delay is the same, still 10secs.

The difference is that the 5.x version now honours your preferences regarding \"leaving apps in memory\' at benchmark time.

If your prefs are set to leave in memory, then the benchmark does not remove the app (and can\'t trip over the 10sec timeout).
If your prefs are set to remove from memory, then the benchmark removes the app and you still have the 50/50 chance of an abort.

Moral of the oral:
When switching from 4.45b to a v5.2.x client, also make sure that you change your preferences to \"Leave applications in memory\". (And don\'t forget to click update from the client to get the updated preferences....)

The delay is the same, still 10secs.

If your prefs are set to remove from memory, then the benchmark removes the app and you still have the 50/50 chance of an abort.

Have you done any testing to confirm this?

I only ask because I ran a load of benchmarks with Boinc 5.2.1 and the spinup pre-alpha and public project. Although I found that benchmarks can still timeout and abort before the applications had terminated, BOINC never failed to restart the apps when they exited.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

If your prefs are set to remove from memory, then the benchmark removes the app and you still have the 50/50 chance of an abort.

Have you done any testing to confirm this?

I only ask because I ran a load of benchmarks with Boinc 5.2.1 and the spinup pre-alpha and public project. Although I found that benchmarks can still timeout and abort before the applications had terminated, BOINC never failed to restart the apps when they exited.

I haven\'t tested extensively tbh.
I did some testing with the public project and the results echo your own tests. Benchmarks abort, but BOINC now appears to catch the \'orphaned\' app and restart it.

I would like to do more testing, especially with the sulphur models since they seemed to be more susceptible to this problem. As soon as I get the time...:)

And we have a new version 5.2.7 available from the same download location http://boinc.berkeley.edu/download.php

I have just installed it, and it seems to calculate the \'To completion\' time a bit better than the earlier versions. Still a bit off, but closer to reality.

And we have a new version 5.2.7 available from the same download location

I gave it a whirl at home last night, and I\'m not impressed.

I use a modem for connectivity there and even with n/w access suspended, it continually tries to send trickles and can\'t resolve the cpdn hostname. Also with n/w access suspended, it was popping up a box asking if \"it\'s OK to connect\". The network options weren\'t being remembered. Regardless of what I set, it just went back to \"Automatically detect\". Then after I\'d connected and allowed network connectivity, the daemon (installed as a service) just died with no explanation in the middle of my uploads and left the manager connectionless.

I remember the days when n/w access disabled meant exactly that. It included trickles, master file fetches, scheduler requests and any other client/server communication, not just uploads and downloads. Disabled means DISABLED damnit! :(

Needless to say, I went back to 4.45 !

Perhaps 5.2.7 may be the recommended version for \"always on\" systems, but modem users beware. The irony is of course that, if I remember correctly, not long ago the v5.x series was touted to be the modem users\' best friend. This may be true of the scheduler code, but the networking code is killing it for me.

[rant mode off]

I\'ve long been a staunch supporter of the BOINC concept, but if 5.2.7 is anything to go by, it is really starting to look like we\'re heading 180 degrees off course. It\'s just too buggy for my liking. I can\'t even defend it as \"alpha\" or \"beta\" software because it\'s the recommended version! At this point I can only feel sorry for new users.

Hi,

That\'s strange enough because in Linux, CC 5.2.7 is working very well (one of the best version I\'ve seen so far)
I have a broadband connection but Boinc is always in \"network connection suspended\" state and it is really suspended (no prob with trickles and the spinup model generates a lot of them) except when I try to attach to a project via the Wizard (I can attach correctly)

The only problem for me is the \'estimated completion time\' that is not realistic even when changing the value in the \\duration_correction_factor\\ tag.
That\'s a problem because Boinc is always in EDF mode and almost never in round-robin mode and newbies don\'t understand why Boinc is stuck with one project and doesn\'t crunch the other ones.

Some members of my team have also reported problems with proxy settings in Windows.

---

Arnaud

And we have a new version 5.2.7 available from the same download location

I gave it a whirl at home last night, and I\'m not impressed.

I use a modem for connectivity there and even with n/w access suspended, it continually tries to send trickles and can\'t resolve the cpdn hostname. Also with n/w access suspended, it was popping up a box asking if \"it\'s OK to connect\". The network options weren\'t being remembered. Regardless of what I set, it just went back to \"Automatically detect\". Then after I\'d connected and allowed network connectivity, the daemon (installed as a service) just died with no explanation in the middle of my uploads and left the manager connectionless.

I remember the days when n/w access disabled meant exactly that. It included trickles, master file fetches, scheduler requests and any other client/server communication, not just uploads and downloads. Disabled means DISABLED damnit! :(

Needless to say, I went back to 4.45 !

...

Did that behaviour start with 5.2.7 or any 5.2.x version?

And we have a new version 5.2.7 available from the same download location

I gave it a whirl at home last night, and I\'m not impressed.

I use a modem for connectivity there and even with n/w access suspended, it continually tries to send trickles and can\'t resolve the cpdn hostname. Also with n/w access suspended, it was popping up a box asking if \"it\'s OK to connect\". The network options weren\'t being remembered. Regardless of what I set, it just went back to \"Automatically detect\". Then after I\'d connected and allowed network connectivity, the daemon (installed as a service) just died with no explanation in the middle of my uploads and left the manager connectionless.

I remember the days when n/w access disabled meant exactly that. It included trickles, master file fetches, scheduler requests and any other client/server communication, not just uploads and downloads. Disabled means DISABLED damnit! :(

Needless to say, I went back to 4.45 !

...

Did that behaviour start with 5.2.7 or any 5.2.x version?

5.25 and 5.26 work perfectly, network suspended means network suspended............

---

Did that behaviour start with 5.2.7 or any 5.2.x version?

Only tried 5.2.7 on this particular system.

5.25 and 5.26 work perfectly, network suspended means network suspended............

On other systems both 5.2.1 & 5.2.2 also suspend network.
[edit]
But they are \"always on\" & have no dial-up capability configured.
[/edit]

It\'s probably something specific to my setup, so here it is if anyone cares to replicate:
System is XP pro, SP2
Dial-up networking configured with 4 dial-up entries.
10/100 Network card installed, media disconnected.
System running BOINC 4.45 (CPDN & Rosetta) installed as service with network disabled until some trickles are pending.

Starting with 4.45 running.
Suspend BOINC.
Stop Service.
Uninstall 4.45 by launching boinc4.45 installer and selecting \"remove\".
Install 5.2.7 as service.

Observed:
BOINC tries to trickle up, even before completing the mandatory version change benchmark.
BOINC continues trying to trickle up even though network access is suspended.

Knock yourselves out. ;-)