In message <o1rqfLA0JgnEFx0o@blueyonder.co.uk>, at 03:26:28 on Sun, 25 Jun 2006, Bill Jillians <"\"Bill Jillians\""@blueyonder.SPAM_NO_THANKS.co.SPAM_OFF.uk> wibbled

Quietly we read <WAwuXSWYiFnEFwBw@user-unknown.mx2.org.uk>, unable to contain our credulity we realized that Pedt <"\"@ @\""@user-unknown.mx2.org.uk> said this:

Computer P3-600, 96Mb RAM, Windows 98SE
Unit 23mr99aa.20172.3218.223594.2.14_1
I think the most important point which isn't covered in your thread is how little resources this WU is using compared to the usual 100% commitment when set to "always run".

I had one of the problem WUs a bit ago. 2 days and counting when the longest previously was ~12hrs. It was using IIRC about 10% of CPU time when I noticed and aborted it. Have a look at the other results from others for the unit. I'd guess that you'll find, like I did, they've all got errors.

I've had 3 more problem units.  Every unit I got yesterday was a problem.  I don't know whether to give it a break or crunch for 2.5 times as long as they usually take.

Worth seeing if they appear listed in the thread referenced before
<http://setiathome.berkeley.edu/forum_thread.php?id=31554>
or on the list Eric Korpela has put up
<http://setiathome.ssl.berkeley.edu/~korpela/bad_groups>


The other thing to be aware of is that 0.226 and 0.25 AR workunits
take significantly longer - so check the ARs. See the table within
<http://setiathome.berkeley.edu/forum_thread.php?id=30625#347698>