In a nutshell, I share one of the computers that I've installed BOINC on with someone else, and, from time to time, that person decides to go through the Task Manager and kill off anything "foreign" to Windows, even though I've shown him how to gracefully exit these programs without losing any data.

And, it seems that, when this happens, BOINC interprets the job that was killed as being completed (or at least this happens with QMC@Home), which is obviously not the case.

My question being - besides BOINC simply marking a killed job as completed, sending it off and eventually having the server reject the results upon comparison, is there a workaround that would allow the jobs to be resumed later (besides not having jobs running when I'd expect him to use the computer, as that's not exactly predictable...), is it feasible that the above could be an enhancement request for BOINC, or would this have to be implemented by individual projects (or has this already been implemented/discussed/etc.)?

Thanks in advance,
-Harrison N.

BOINC doesn't mark anything as completed. It is the science application that does so. Remember, BOINC doesn't crunch anything, it just manages all the applications for the various projects, upholds the communications and the queues for the projects.

So in this case, you'd best ask on the QMC forums for a more sturdy application, one that doesn't immediately kill tasks when they are stopped in the middle of crunching. Checkpointing helps. ;-)

---