Unaccountably, I cannot stop downloading n-body cpu type tasks on one of my systems processing MilkyWay. This is unique as on my other systems I am able to prevent cpu tasks from downloading when I dont want them. Rather than detach and re-attach to fix the problem I was hoping to figure out what went wrong and why this particular system has a problem in case the others start misbehaving.

Temporarily I deleted the executable applications from the milkyway project directory. These CPU tasks no longer run, but they do keep downloading.

I looked through the wiki on client configuration and see only gpu exclusions.

Is there a way to specify a cpu app from being downloaded in cc_config or app_config?

I assume this is punishment for using GRCPOOL to handle my downloads.

Project preferences -> uncheck "Use CPU".

---

Jord: the option is "No CPU" and I have it checked. All my other system have "No CPU" checked for MilkyWay and they do NOT get cpu tasks. Something is wrong.

Could this be a case of "lost tasks" that are being resent? Maybe that avoids looking at the [X] that says do not send CPU tasks.

Any lost tasks would show on the project web site - they're only 'lost' from the client. They're also noted as resends in the event log.

But yes - I do believe lost tasks bypass the "don't use..." selection. The wording has possibly changed over the years - the checkbox is labelled "Use CPU" at projects using the most recent version of BOINC.

You should also see "Don't request tasks for CPU" in the project properties in BOINC Manager if that option is set on the project website.[That's using BOINC Manager - your screenshot seems to come from a different tool]

And as an added wrinkle, when MilkyWay first added mt tasks (known as n-body) to their website, some years ago, they classed them as GPU tasks...

I detached and then re-attached. This fixed it. I waited until most of the tasks completed. AFAICT there is no way to exclude non-gpu tasks. This was NOT a problem with "lost" tasks. It is a grcpool manager implementation.

Wanted to follow up on this post to explain more fully how I fixed the problem and why it is a grcpool defect.

I used boinctasks but I assume boinc manager behaves the same way: When using a project manager such as BAM!, I have noticed that I cannot detach a project from my local manager. I have to go through the project manager to do a detach. Apparently, this is not the case with grcpool's manager.

I checked the box to detach milkyway from the grcpool manager. That didnt work, it should have. I then found out I could issue a local command to detach. This should not have happened as grcpool is the manager. Unless policies have changed recently, BAM! would have never let me detach that way.