Hi,

I have the strange behavior that the 5.10.45 Boinc client on Ubuntu 7.10 is behaving strangely when I change some of the settings under "Activity".

The machine is has a 4-core CPU.

It happens sometimes that, after I click for example "Network activity suspend" that it begins to alternate the states between suspended and active network status.

Here I manually suspended network activity in the network client -->
Wed 12 Mar 2008 08:36:47 AM CET||Suspending network activity - user request
Wed 12 Mar 2008 08:36:49 AM CET||Resuming network activity
Wed 12 Mar 2008 08:36:50 AM CET||Suspending network activity - user request
Wed 12 Mar 2008 08:36:52 AM CET||Resuming network activity
Wed 12 Mar 2008 08:36:53 AM CET||Suspending network activity - user request
Wed 12 Mar 2008 08:36:54 AM CET||Resuming network activity
Wed 12 Mar 2008 08:36:55 AM CET||Suspending network activity - user request
Wed 12 Mar 2008 08:36:56 AM CET||Resuming network activity

When opening the "Activity" Menu I could see that the radio button alternates between both states.
I then again clicked on the "network activity suspended" button and it stopped alternating.

Anyone else see that behavior?

Same goes for computation state...

Cheers
PJ
Wed 12 Mar 2008 08:36:57 AM CET||Suspending network activity - user request

Just yesterday this version was declared 'recommended'. Could it be a sticky keyboard.... seriously, I've found at times that holding the mouse key a little longer makes things hold. Why I don't know.... maybe overall systems load.... happens on my Vista Quad at times.

I have another machine (Dual-Core this time) that does not display such a behaviour. So it is not a general error of the Manager Version.

What it looks like is that one core is checking what state the configuration file is in while the other core is writing the change to the configuration file. Then they switch roles as they discover a delta. Or something like that. It stops when I click the actually "not-pushed" radio button.

I've seen this behaviour when two managers were controlling a single client (i.e., one local and one remote). One keeps telling the core client to suspend, and one to resume.

---

I've seen this behaviour when two managers were controlling a single client (i.e., one local and one remote). One keeps telling the core client to suspend, and one to resume.

No remote control here. Just the BOINC 5.10.45 Manager.

Interestingly it went away after a reboot.

It, the manager, did make a CPU Benchmark because of version change though ( 5.10.42 --> 5.10.45 ) so that seems to have been deferred, too.

No remote control here. Just the BOINC 5.10.45 Manager.

You could still have two managers running at the same time; on the same computer.

---