How do I get rid of a borked WU?

2bullish

2bullish

2bullish

Associate
Joined
21 Jan 2005
Posts
762
Location
Manchester
As the title says I have project 772 worth 149 points but for some reason it is taking an age to complete, can I delete this WU and get another as its telling me its going to take two weeks :eek:
 
If you really feel the need to get rid of it then just stop the client, nuke the work folder and restart the client.

Are you sure there is a problem and it's not just something to do with the GPU client [if you are running it] or something else nicking CPU time?

SiriusB
 
SiriusB said:
If you really feel the need to get rid of it then just stop the client, nuke the work folder and restart the client.

Are you sure there is a problem and it's not just something to do with the GPU client [if you are running it] or something else nicking CPU time?

SiriusB
Click to expand...

Hey Sirius, no I'm not running the GPU client on that machine and also I have the same WU on another similar machine that saying completion in a day and a half, must be borked.
 
If monitoring with Fahmon it needs some checkpoints to actually work out the time it's going to take. Sometimes it just seems to put up a silly time rather than N/A. Also perhaps SSE didn't kick in assuming your using a CPU with SSE. :)
 
oceaness said:
Also perhaps SSE didn't kick in assuming your using a CPU with SSE. :)
Click to expand...
that would be my guess - restarting the client would have got SSE working again anyway

it's best to use the -forceasm flag to avoid things like this (caused by messy restarts/crashes) unless you're already using -forceasm in which case the WU may have got corrupted or something
 
9/10 of the time you get the exact same WU back anyway, so assuming you weren't about to finish no one really loses out from the nuking of a WU.

Stanford still get their WU results, just a little later and you still get the points, just a little time is lost.

SiriusB
 
rich99million said:
that would be my guess - restarting the client would have got SSE working again anyway

it's best to use the -forceasm flag to avoid things like this (caused by messy restarts/crashes) unless you're already using -forceasm in which case the WU may have got corrupted or something
Click to expand...


forceasm is on all my machines, tried restarting didn't do anything, must have been a borked WU
 
Yep the server recognises your UserID and the MachineID tagged on the end so sends out the exact same WU you already had - kinda annoying at times but you can always change your MachineID to fool it into giving you something different :p :D


not that I'd ever dream of doing something like that of course :o
 
You must log in or register to reply here.
Back
Top Bottom