For some reason, when running BOINC, I can close the manager, but the BOINC client itself will stop respecting my "only run after 5 minute idle" preference. I can see this because while the manager is closed, the task manager reports BOINC processes (like the wcg projects) as taking up a lot of CPU, but as soon as the manager opens, they drop to 0 usage.

Running version 6.2.18 if that helps.

But BOINC Manager is only a graphical interface that allows you to use commands in an easier way than having to type everything in through the command line. It doesn't add anything to the running of BOINC.

Testing this on my own system I cannot reproduce it.
So the default questions: Which OS? is this 64bit or 32bit BOINC? Are you running as a service? Do you use the web based preferences, or those through BOINC Manager Advanced? What are your other preferences set to?

Can you please post the contents of your global_prefs.xml and if applicable global_prefs.override.xml files? You can find them in your Data directory.

---

But BOINC Manager is only a graphical interface that allows you to use commands in an easier way than having to type everything in through the command line. It doesn't add anything to the running of BOINC.

Testing this on my own system I cannot reproduce it.
So the default questions: Which OS? is this 64bit or 32bit BOINC? Are you running as a service? Do you use the web based preferences, or those through BOINC Manager Advanced? What are your other preferences set to?

Can you please post the contents of your global_prefs.xml and if applicable global_prefs.override.xml files? You can find them in your Data directory.

Using web based preferences, 32bit BOINC client. Running BOINC as service (I think that's what protected app mode install does anyways).

Note: Behavior disappeared with upgrade to 6.2.19. Also brought a new process with the default boinc.exe; boinctray.exe which stays even if boinc manager is quit. Should I continue to post prefs file, or would this be considered resolved?

I'm having the same issue with the project continuing to work and boinctray and boinc.exe still running after boincmgr has been closed down.

I'm running 6.2.19 on WinXP Home SP3

Shutting down the manager in BOINC V6 does NOT shut down the daemon, which does the actual work. This manager is just an easy way to see what BOINC is doing.

Have a look at the last section of this 'sticky', which is at the top of Questions and problems: here

But BOINC Manager is only a graphical interface that allows you to use commands in an easier way than having to type everything in through the command line. It doesn't add anything to the running of BOINC.

I think the manager also has input detection built-in and sends that to the core client.

boinctray was made for cases where boincmgr doesn't run on startup for all users in the computer.

---

I'm having the same issue with the project continuing to work and boinctray and boinc.exe still running after boincmgr has been closed down.

That's how it's supposed to work. Turning your screen off doesn't shutdown the computer. BOINC Manager and the core client are the same.

---

I think the manager also has input detection built-in and sends that to the core client.

boinctray was made for cases where boincmgr doesn't run on startup for all users in the computer.

[off-topic]Now I'd like to let the client slip the idleness' status through to the applications (maybe 1 boolean along the heartberat message), to let them know about. Or have I missed somehow it is happening already?[/off-topic]

Peter