well all but 1 result is valid now, have 6 days...
I'd be grumpy, but have PLENTY of UGM so I won't cry yet,
until I have 2 years at least (long time with 1.5 comps working).
Just got a job though,
so might consider a new Super cruncher...
Then I'll be ready for the flood when they get to it.

If this was supposed to be in jest then it was irresponsible none the less. Don't defeat the BOINC client backing-off algorithm - it is there for good reason.

I would hope that the World Community Grid scheduler has velocity checks in place to limit the damage that such selfish robotic forced updates could do, but I doubt it. I'd throttle back devices with a poor work to update ratio and send them away empty-handed to defeat such strategies. If that doesn't stop them then blacklist their IP addresses and refuse their connections until they behave nicely.

If you get enough people doing this often enough you would bring down World Community Grid by overloading its scheduler. It would amount to a denial of service attack. That's unfair on the entire community, especially the scientists with projects for which there are plenty of WUs available, who can no longer get them out.

The fair and acceptable ways of getting OET WUs have been documented: top up with other projects and get OET as and when the WUs become available and your systems chance upon them.

If you get off on collecting badges by cheating then this is probably the wrong community to be in.

BOINC has a built-in protection for force update. And you will receive a message like this:
World Community Grid | Not sending work - last request too recent: 1 sec

WCG requires 121 sec at the moment before you can issue an update and get WUs.

That CRON (linux) command would force update every 3 minutes.
As Sandvika said, irresponsible.
(before edit the original post requested each hour at 3 minutes past)
"3 * * * * boinccmd --project http://www.worldcommunitygrid.org/ update"

Paul.

Amen ! 1+

CJSL

Crunching like there's no tomorrow...