Joined: 28 Jun 07
Totally my fault. Closing down some unneccessary tasks and accidentally stopped this wu . It didn't take kindly to that and showed up as computer error and looking in client_state showed the catch-all -161. Thinking that I might be able to trick it into restarting, I deleted all these error lines but it then couldn't find other bits and dissappeared completely, so I can't even abort it now, so Acmefrog will have to wait for it to timeout and then be be reissued, sorry.
Anyway, this prompted an item more for a Boinc wishlist rather than just here, but those better connected than me could maybe pass on the suggestion.
Currently the command options for a running wu are:
How about adding:
Restart just for idiots like me who break a wu partway through so that the wu will begin again with its initial parameters intact as if it had just been downloaded. Obviously there would then need to be a safeguard "confirm restart" message so that nobody would accidentally restart a 4 month old CPDN model, for example, but restarting shorter wus such as these after a user error wouldn't result in much repeated work and might save some time in projects not having to reissue work.
Just a suggestion. Any thoughts?
Update 10 minutes later:
Did an update to see if it would report the wu as lost and back came the reply;
28/07/2007 21:13:58|Cosmology@Home|Message from server: Resent lost result wu_072407_053211_0_0 and then it redownloaded the neccessary files again so I can crunch it uninterupted overnight and I'll not interfere with it this time.
Joined: 8 Jun 07
Totally my fault. Thinking that I might be able to trick it into restarting, I deleted all these error lines but it then couldn't find other bits and dissappeared completely, so I can't even abort it now, so Acmefrog will have to wait for it to timeout and then be be reissued, sorry.
We all screw up WUs one time or another. Now stay away from the computer. :)