Hey, who did the WU for me?

[Ken g6]

I just noticed this in my OK SetiQ History:

ASUS.1625728.3.3.i386-winnt-cmdline

With a 7 hour WU, so I know it's not one of my Athlons.

So, thanks! 😀 But who was it? 😕

 

[Engineer]

It could have been one of the OK SETIQueue mixup WU's...seems that OK's Queue changed some of the userinfo.sah files on some of the WU's sent out after/during the CRASH...

🙁

It's been a problem floating around...so check your user_info.sah to make sure all the WU's have the correct ID...

🙂

 

[micron]

It's probably related to the recent problem with OK's proxy. Someone's user_info.sah must have gotten switched with yours.

 

[ShotgunSteven]

Once the WU's with the incorrect info are done and sent in, will that take care of the problem, or will it continue?

 

[teriba]

It will continue.

 

[Ken g6]

Well, I'm starting to feel guilty about taking WUs from a stranger. 😱 So if anybody wants to come forward (even if you don't feel the need to correct the situation 😉) the WUs are coming from:

Name: *.strhg1.mi.home.com
Address: 24.255.193.108

Whoever it is must have about 2 stray members of their herd.

And whoever you are, thank you. 🙂

 

[Pyxis]

<< Well, I'm starting to feel guilty about taking WUs from a stranger. 😱 So if anybody wants to come forward (even if you don't feel the need to correct the situation 😉) the WUs are coming from:

Name: *.strhg1.mi.home.com
Address: 24.255.193.108

Whoever it is must have about 2 stray members of their herd.

And whoever you are, thank you. 🙂 >>




That's my ip. I had the exact same problem with my SetiQ yesterday.