Don't worry, WCG Techs will see too it that quorum 2 will be achieved.

As for never claiming that much, just take a regular job you did recently, take the claim divided by the hours and multiply with the hours spend on this long job. You should arrive at your 530 credit request.

Dont' worry about that either. Given the transition period a 3rd copy will be pushed out soon. Why immediately if only 2 are needed. If 2 return quickly, the 3rd would waste CPU time.

Hi Techs,

sorry to say, one of my clients crashed today (had nothing to do with the large FAH wu's), but there was one of those wu's on it, waiting to get crunched...

You can send out the wu "faah5009_1hpv_1b6m_00" again, a new installation of this client was necessary, so this wu has been terminated by format c:

Sorry...

I know, but for this one, it might take long until it gets resent, because the dead-lines have been extended... And it was pointed out, that these wu's are very important, due to the single-redundancy... So, if there's a possibility, send it out again right now, the initial-sent-out-one will not return...



I don't hope so, that client was not one of my 24/7...

hmmm, this is the second report of "exceeded CPU time limit". 209079 seconds is 58 hours. There is a value set based on the normal FAAH size to prevent them from running ad infinitum if looping e.g., but looks that now on the slower machines this is coming to bite with the big jobs. It's probably some multiplicator of the estimated flops contained in the header, which would explain why the previous report stopped at 158,000 seconds.... a guess