Closing remote BOINC manager exits local BOINC service

[Ageless]

I run two BOINC Managers, one to check the local machine (Windows XP Pro SP2 32bit), one to check the remote machine (Windows 2000 SP4). It used to be that when I closed down the BM for the remote machine, that the service on the local machine continued working. This behaviour changed since BOINC 6.6.0, where exiting the remote BM from the system tray will now kill the local service, leaving the BM for that BOINC with the red x in the icon and it complaining it can't find the client.

No warning messages are given on closing the remote BM. Only when I subsequently close the local BM, will it ask me if I want to stop running the science applications etc.

Also see this behaviour on BOINC 6.6.2, but that is to be expected as I only reported this behaviour to the alpha email list this morning.

[romw]

We'll get this addressed as part of a revised exit BOINC manager work-flow.

[Ageless]

Ok, so what changed?

6.10.18 .. closing remote BM closed local client silently.
6.10.19 .. closing remote BM keeps local client running.

Something in the GUI RPCs fixes for .19 perhaps?

[Ageless]

6.10.24 has it broken again. :-(

[Sekerob]

The weird thing is that explicitly setting the 'Exit' dialog several times on and off, there is no dialog appearing, hitting the red x or selecting Close Manager from the menu, just kills the service. Lucid Lynx, 6.10.17. Can't seem to find where the flag is set (nor that for the language), though part of the 'Options' changes is written to the end of client_state.xml so is seen.

Is ticket #814 related?

[Sekerob]

To add, connecting the BM to a remote host and then closing the manager leaves the local service running!

[romw]

I believe these scenarios have been addressed in the latest 6.12 releases.