Warning!!! There Are Still DEFAULT_xxxx_205's Out There!

8 Hours of my time...
11 hours of my time...

This has been a warning by:
cloaked_chaos

Warning!!! There Are Still DEFAULT_xxxx_205's Out There!

yes they are like zombies, when you kill them they just pick on someone else.

Instead of abort, if you suspend them (from the work tab, not from the project tab) they will stay on your box and let Rosetta get on with other work. Then when the project team figure out how to kill them properly, _then_ you can abort them. This is unofficial advice but -- hey -- while the officials are on holiday we need to figure things out for ourselves.

River~~

edit:
edit removed ;-)

---

Instead of abort, if you suspend them blah blah blah...
River~~

This is a big problem for me as I host most of my machines in a different city no less than 100 miles away. (for the free electricity and cooling [65 degrees year round baby!]) So that means strictly no access to the consoles. (too lazy to set up remote desktop)

Instead of abort, if you suspend them blah blah blah...
River~~

This is a big problem for me as I host most of my machines in a different city no less than 100 miles away. (for the free electricity and cooling [65 degrees year round baby!]) So that means strictly no access to the consoles. (too lazy to set up remote desktop)

I've just dicovered BOINCview - it is great if the remote box has a fixed public IP address and so does your internet connection. Otherwise there is more to learn before it works. I'd have taken most of my boxes off Rosetta for the duration of the problems if it hadn't been for BV.

See a discussion of its advantages here

But yes, all these dodgy wu have been a hassle for my remote boxes, and BOINCview can't do everything. 100 miles? Puts my feelings into perspective - I was griping to myself about having to walk a few blocks to mine...


R~~

---

Looks like one of those sat in a cache for 3 days and the other sat in a 2-day cache twice. One has had six victims, the other only five, so we can expect them to hit a few more people before they are finally killed off...

At least you know you'll have a 300+ credit "payday" from these two when the staff gets back! :-)

Next week, expect lots of "my RAC is all funny" discussions on the boards...

---

At least you know you'll have a 300+ credit "payday" from these two when the staff gets back! :-)

300 credits? well, i suppose that is acceptable for the 10 hours lost on my machine, heh.

btw, my rac is all funny...

;)

---

300 credits? well, i suppose that is acceptable for the 10 hours lost on my machine, heh.

Just to clarify in case anyone doesn't understand... the "300 credits" is roughly what the OP claimed on the 205's _HE_ processed, so it's what is likely to be granted if the staff does a straight "grant=claimed" on those. No idea what anyone else would get. I don't speak for the project and don't know what they'll do, just that they said "credit will be granted" on them.

---

Instead of abort, if you suspend them (from the work tab, not from the project tab) they will stay on your box and let Rosetta get on with other work. Then when the project team figure out how to kill them properly, _then_ you can abort them. This is unofficial advice but -- hey -- while the officials are on holiday we need to figure things out for ourselves.

I originally suspended one of these that I found, but after seeing your post in another thread about them being cancelled, it's been aborted and should clear itself now.

---