After rebooting, and while BOINC is starting, clicking "File" and "Exit BOINC" causes the window to close, but it doesn't stop running tasks when the "Stop running tasks when you exit the BOINC manager" has been selected.

How do I report this to the development team?

---

Calm, grasshopper, let's check something first.
BOINC Manager->Tools->Options->is "Enable Manager exit dialog" checked?

---

Yes, of course it is. That is why I GET the exit dialogue that isn't working.

---

After rebooting, and while BOINC is starting, clicking "File" and "Exit BOINC" causes the window to close, but it doesn't stop running tasks when the "Stop running tasks when you exit the BOINC manager" has been selected.

What means "while BOINC is starting"?
Do you try to exit in the first seconds after BOINC is started?
If you wait e.g. one minute after BOINC is started do you have the same problem at exit?

Which Computer ID
http://setiathome.berkeley.edu/hosts_user.php?userid=61201

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

What means "while BOINC is starting"? Do you try to exit in the first seconds after BOINC is started?

Yes.

When the BOINC Manager is first accessible in the first few seconds, I have tried to "suspend" activity (which was ignored).

I have also tried to exit selecting stopping tasks in the exit dialog (which was ignored). It did exit, closing the window, but the tasks continued to initialize and run.

Which Computer ID

http://setiathome.berkeley.edu/show_host_detail.php?hostid=5111135

This is my workhorse, and I also run Rosetta and other projects on it. Rosetta puts a heavy load on the disks during startup, so when I found the other bug (see http://setiathome.berkeley.edu/forum_thread.php?id=74780), which caused a long, unacceptable startup, I tried to get BOINC to stop. Then I could have set "% of processors" to 1, then 2, etc. until it was back to running all without killing my high priority work.

[Edit] To answer your other question, it works normally and as expected AFTER all the tasks are running. With Rosetta on all 8 logical CPUs, though, means about 5 minutes.

---

Then probably in the first few seconds after BOINC is started boinc.exe and/or the apps are in some initializing phase and still don't listen to the commands from boincmgr.exe

"It did exit, closing the window" = boincmgr.exe exited
"... but the tasks continued to initialize and run." = boinc.exe did not receive the command
(boincmgr.exe gives-up in a few seconds if boinc.exe do not respond and exits)


Did you try to use boinccmd.exe instead?
Shortcut with command similar to this:
.....\BOINC\boinccmd.exe --set_run_mode never 333


(boinccmd.exe sends commands to running boinc.exe - it does not need boincmgr.exe to run)
http://boinc.berkeley.edu/wiki/Boinccmd_tool

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)