My Setiqueue ..........Error Log Files.....

[Smoke]

Originally posted by: Coolkid
Wouldent you need to delete all the .sah files in the directory?
The RESULT.SAH file is just the result, which would mean that it would restart, find no result.sah file and just start processing the defective WU again?

If you are running SetiDriver or SetiHide you would want to delete the entire folder of the WU containing a "result.sah" file. So in that instance you are probably right ... I have not verified this but it makes sense.

If you are running Seti as a Service this is what I believe happens. When a Service finishes a WU all associated files except the "result.sah" file are deleted and the "result.sah" file is transmitted to Berkeley. Since Berkeley refuses to accept the "defective result.sah file", the Service is stuck with nothing to do. It can't download a new WU until the result.sah file is transmitted (and then deleted) so it just sits there. I'm guessing this is what is going on because it has been verified that by deleting the "defective result.sah file" and rebooting the computer, a Seti Service can get going again. 🙂

 

[Coolkid]

Ah, that makes sense 🙂