BOINC is stuck running benchmarks.

It can not complete benchmarks, so it tries again, and again and again.

How can I get it to forget about the benchmarks and just crunch?

Hi Pat,

Start to say I did not try it myself , but in the client_state.xml you will find at the very beginning host_info.
In that part is also a line "<p_calculated>1232491303.674892</p_calculated>" of course with a similar number.
This is the time benchmark has runned the last time.
After stopping the Boinc client and modifying the number into 1232861303,674892 and restarting the Boinc client your problem could be solved for lets say the next 4 or 5 days. So you only have to change the digits on place 4, 5 and 6.

Good luck!

What if the number was 0.000000000?
What do I change that to?

Nevermind, I think I figured out what I need to do.

Hopefully, will have good news to report soon...

Ok, I'm making progress...

Is there a way to either lie about how much RAM I have avalible, or make BOINC think that my swap is actually avalible RAM?

Trying a little experiment...

Oooh... Not the best idea. Hitting swap really slows down a computer. If you have to run a project by moving things into or out of swap, that's going to slow things down quite dramatically.

I'm not trying to do this for the speed, it's a matter of pride.
See here.

You have/had a problem with the systemclock, when you had this benchmark problem.
I think you figured that out in the meantime.
0.0000000 means that Boinc was thinking your last benchmark check runned on 01-01-1970:00:00:00.
That date is a kind of initial timestamp for computer programmes and the number in my example is the amount of seconds since 01-01-1970:00:00:00.