Project 7611 (0, 23, 259) - High TPF

[DrSpalding]

How exactly do I dump a WU? I am running the service version of v7 on Win7 x64. I am assuming I can pause the core/client, stop the service, and then poke around and kill all the data/work files associated with the WU?

[PantherX]

That would be one way. Another (untested) way would be to boot into safe mode (that ensures only vital services are running), delete the correct work folder and then boot normally. If you use this untested method, please report back if it was successful or not. Thanks.

[DrSpalding]

Also wondering what the statement by Bruce, "Note that the list of reported WUs are stopped daily at 8am pacific time." actually means. Does that mean that there is a way that FaH can tell the fahcontrol to stop working on the wu immediately?

I'll go ahead and kill the stuff and let you know.

[DrSpalding]

I paused the WU, stopped the FAHControl program, and stopped the service via the command:
net stop "Folding@home Client"
in an administrator command prompt.

I then deleted the "01" directory in \fah\data\work and restarted the service via:
net start "Folding@home Client"
in the administrator command prompt.

It started up as normal like on a reboot and got a brand new WU downloaded, an P8084 WU, and it is working just fine on it.

[PantherX]

Also wondering what the statement by Bruce, "Note that the list of reported WUs are stopped daily at 8am pacific time." actually means. Does that mean that there is a way that FaH can tell the fahcontrol to stop working on the wu immediately?...

It just means that all the bad WUs that are reported by the Moderation Team will be processed on 8am pacific time. Thus, those WUs will not be assigned anymore after that time. (It prevents the server from assigning the uncompleted WUs to other people.) However, if you did get them before 8am, your FAHClient will continue to process it and possibly fail since it is a bad WU. The Server cannot instruct a FAHClient to kill a WU automatically. That is only possible on the donor machine by donor action or hardware issues.

[DrSpalding]

Also wondering what the statement by Bruce, "Note that the list of reported WUs are stopped daily at 8am pacific time." actually means. Does that mean that there is a way that FaH can tell the fahcontrol to stop working on the wu immediately?...

It just means that all the bad WUs that are reported by the Moderation Team will be processed on 8am pacific time. Thus, those WUs will not be assigned anymore after that time. (It prevents the server from assigning the uncompleted WUs to other people.) However, if you did get them before 8am, your FAHClient will continue to process it and possibly fail since it is a bad WU. The Server cannot instruct a FAHClient to kill a WU automatically. That is only possible on the donor machine by donor action or hardware issues.

Thanks. That's what I thought but wanted to be sure. If there was a way to control it from Stanford's end, I would have just let it go, since it was ~08:00 PDT today when I cleaned it up manually.

[bruce]

Cleaning it up manually (locally) can often induce the server to note that nobody has finished that WU and to reassign it. In cases like this we don't want to inflict the same problems on somebody else, even if you've gotten rid of the copy that was assigned to you.