There are a number of projects which work rather like a shell, in which work from a number of sub-projects can run. If you select a couple of the sub-projects, then work from those selected arrives and gets done. There is usually a box to check which says something like "if no work is available for your chosen sub-project accept work from one of the others", ie. those that you have specifically chosen to exclude. This appears to default to "Yes". I think that should default to "No". You have stated that you want work from certain projects and NOT the others, yet it will send work from the ones you have rejected because the "Yes" in the box I mention above says it can. There could be important reasons why the choice was made.

This has happened to me at LHC.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Post this issue to the BOINC Github forum as an issue with the configuration files to change that default to NO. But you would still be dependent on each projects admins to not change the default server configuration files.

The thing though is, by default BOINC is made to have work in cache, not to sit idle. So then the setting for "If no work for selected applications is available, accept work from other applications?" makes sense, because then by default BOINC will never (easily) be without work and just sit idle for days on end until you return and notice that... and then complain about that fact.

---

The thing though is, by default BOINC is made to have work in cache, not to sit idle. So then the setting for "If no work for selected applications is available, accept work from other applications?" makes sense, because then by default BOINC will never (easily) be without work and just sit idle for days on end until you return and notice that... and then complain about that fact.

I think this day and age, this would not be the case.
Most people run more than 1 project per PC.
It would make sense if LHC was the only project your PC runs.
But also I turn it off to most projects, as I am very selective in what projects I want to give my resources to. And am not interested in providing services to a project that (in my opinion) doesn't really need it.

He's right Jord, leaving the machine workless is not really an issue. What IS an issue, is UNWANTED work being sent. Even if it was, you'd consider it okay to send a type of work to a volunteer cruncher that had already refused to accept?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

>>> Post this issue to the BOINC Github

I don't seem to be able to log in there...

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

You're purely looking from a user perspective, your own. And it's easily fixed for you by going to the Projects preferences page and unchecking that option. What I said was that it's a default BOINC function and here it doesn't matter if you have one project added or 24. There comes a day when all but one project have no work and that one project does have work but not for the application you selected to run. So then your computer sits idle.

As a user you still have responsibility in setting things up correctly, you can't just leave it all to BOINC to be automated. And what you want as a preference on this (default off) another user will want default on (like me). There's no pleasing, no middle way.

---

>>> So then your computer sits idle.

And it sits idle because I have made that decision. A decision I have made with regard to MY resources.

Sad. Jord Reputation --

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Sad. Jord Reputation --

You've been told what to do by Keith yet you blame me?
Welcome to my ignore.

... and I said why I could not.

>>> Blame? Explain.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I am with Jord on this.

There is no middle way but I am happy to turn off the option - WCG I only accept Africa Rainfall Project for instance and don't accept anything else if it isn't there. I accept that some perhaps many will have a different view on this but hope it isn't as divisive as Brexit!

I also like it the way it is.
I'm quite capable of adjusting pref settings myself.

>>> Post this issue to the BOINC Github

I don't seem to be able to log in there...

Have you made an account at Github yet. It is not your BOINC login.

I'm with the OP on this. The point of selecting subprojects is that you only want to run those, not any others, and if that's the only project you're running it should be obvious that you're ok with an idle machine. How many times in these and project forums have we seen people asking why they're getting work that they didn't select? Most of time it's because they overlooked the "accept other work" checkbox, which is easy to miss if you're not aware of it. Frankly I'd be fine with the "accept other work" going away completely. If you're worried about idle machines the sensible thing to do is select everything.

---

Team USA forum
Follow us on Twitter
Help us #crunchforcures!

I'm with the OP on this. The point of selecting subprojects is that you only want to run those, not any others, and if that's the only project you're running it should be obvious that you're ok with an idle machine. How many times in these and project forums have we seen people asking why they're getting work that they didn't select? Most of time it's because they overlooked the "accept other work" checkbox, which is easy to miss if you're not aware of it. Frankly I'd be fine with the "accept other work" going away completely. If you're worried about idle machines the sensible thing to do is select everything.

Better yet,check a subproject box and it automatically unchecks the other work box.