How to figure out which WU your SetiDriver is currently processing?

[Smoke]

I have a problem WU that seems to be stuck. Using SetiDriver and the CLI Client.

Is there a way to tell which WU is being worked on so it could be deleted? In the past I have always deleted the whole package and started over but with WUs in short supply I am reluctant to do that. I'd appreciate some advice on figuring out which WU to delete.

 

[conjur]

Smokeball,

I just use the Windows Explorer and highlight each sub-folder under the SETI CLI folder (there's one for each WU cached) and check the state.sah file looking for it to be non-zero bytes in length and have the current date/time as the date/time stamp.

 

[Smoke]

Thanks conjur, I'll give that a try right now. 🙂

 

[conjur]

No warranties or guarantees, written, expressed, nor implied.

😉

 

[Confused]

If you put SetiWatch into the main Seti directory, then under Options -> Seti Locations, select the Seti folder on your computer, check the little box saying "Using caching program", click OK, then go to analysis tab, and there will be Smoke (3) where (3) is the folder where the WU being worked on is 🙂

You can also use this to monitor computers across a LAN, by placing it in the seti directory and sharing the directory on the network 🙂 Useful for seeing when a client is down!

ConfusedBW

 

[Smoke]

I found that I can do a file search for "state.sah" and I get a result report that makes finding the WU quiet easy. Thanks again, conjur.

 

[Smoke]

Another question: There are two state.sah files with greater than 0 bytes. One is in a number folder but there is another one in the Seti folder root directory. Should that one be deleted also?

 

[conjur]

Probably so, Smokeball.

I bet the date stamp is quite old. If you run the CLI in that folder before SETI Driver and connect to Berkeley, you'll get a set of files for processing in that main folder. You can toss it. But keep the user_info.sah (at least I do)

 

[Smoke]

ConfusedBW, I have not had good luck with the latest version of SetiWatch, Version 419, and have reverted to the previous version which does not have that option. 🙁

I actually went there first. 😉

 

[Confused]

Oh, i have been using that version (one pointed to in link above) on my machines for quite a while, and i've had no problems with it! 😕

Oh well, so long as you've sorted it out 🙂

ConfusedBW

 

[Smoke]

I downloaded the 4.1.1 version that you have linked and it seems to work fine. 🙂

 

[Confused]

Wow, one of the few times i'm behind in app versions it comes in useful to others! 🙂

Glad it works Smoke 🙂

ConfusedBW

 

[BigFatCow]

for the seti driver question (even though it was already answered), an easier way would just be to click off "hide processing" and then when the dos window shows see what number it is...

 

[Smoke]

BigFatCow gets the "best idea" award for this. How simple. I love KISS. Thanks everyone for the help. 🙂