And I wonder what this is going to do to all of the 'set and forget' hosts...
Folks that attached to the project on a whim and have long since forgotten it is running in the background. There are probably many thousands of them.

Might the project have to issue some kind of DCF reset command to coax them back into action? Is that even possible?

If they simply attached, they don't have a problem - none of this, thankfully, is affecting users of the stock application, since stage 2 of the bungle - fortunately - wasn't applied as scheduled on Friday.

But there are some 'set and forget' types who got as far as installing an optimised application (or having one installed for them) during the 'set' phase, and have now proceeded to 'forget' - we know that from the V12/Fermi hall of shame. Those are the ones that will be caught, unless the project itself manages the situation carefully.

And I wonder what this is going to do to all of the 'set and forget' hosts...
Folks that attached to the project on a whim and have long since forgotten it is running in the background. There are probably many thousands of them.

Might the project have to issue some kind of DCF reset command to coax them back into action? Is that even possible?

If they simply attached, they don't have a problem - none of this, thankfully, is affecting users of the stock application, since stage 2 of the bungle - fortunately - wasn't applied as scheduled on Friday.

But there are some 'set and forget' types who got as far as installing an optimised application (or having one installed for them) during the 'set' phase, and have now proceeded to 'forget' - we know that from the V12/Fermi hall of shame. Those are the ones that will be caught, unless the project itself manages the situation carefully.

Of course, no matter how carefully the PROJECT may proceed, they are at the mercy and foibles of the Boinc code supplied.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

It's been such a long time.......
I don't recall if a reset will chuck out the baby with the bathwater...IE, the optimized apps and app_info file. A detach certainly does.

Ditto. I've got a couple of boxes with nothing cached and only a few tasks waiting to upload - I've set NNT on them (they're happy enough crunching Einstein and GPUGrid), so I don't get any surprises before I get a chance to experiment once the upload server is back.

And I wonder what this is going to do to all of the 'set and forget' hosts...
Folks that attached to the project on a whim and have long since forgotten it is running in the background. There are probably many thousands of them.

Might the project have to issue some kind of DCF reset command to coax them back into action? Is that even possible?

If they simply attached, they don't have a problem - none of this, thankfully, is affecting users of the stock application, since stage 2 of the bungle - fortunately - wasn't applied as scheduled on Friday.

But there are some 'set and forget' types who got as far as installing an optimised application (or having one installed for them) during the 'set' phase, and have now proceeded to 'forget' - we know that from the V12/Fermi hall of shame. Those are the ones that will be caught, unless the project itself manages the situation carefully.

Of course, no matter how carefully the PROJECT may proceed, they are at the mercy and foibles of the Boinc code supplied.

Feel free to remind David that he is still listed as Director of SETI. For the purposes of the current discussion, the project and BOINC have to be thought of as (and actually behave as) members of the same team.

And I wonder what this is going to do to all of the 'set and forget' hosts...
Folks that attached to the project on a whim and have long since forgotten it is running in the background. There are probably many thousands of them.

Might the project have to issue some kind of DCF reset command to coax them back into action? Is that even possible?

If they simply attached, they don't have a problem - none of this, thankfully, is affecting users of the stock application, since stage 2 of the bungle - fortunately - wasn't applied as scheduled on Friday.

But there are some 'set and forget' types who got as far as installing an optimised application (or having one installed for them) during the 'set' phase, and have now proceeded to 'forget' - we know that from the V12/Fermi hall of shame. Those are the ones that will be caught, unless the project itself manages the situation carefully.

Of course, no matter how carefully the PROJECT may proceed, they are at the mercy and foibles of the Boinc code supplied.

Feel free to remind David that he is still listed as Director of SETI. For the purposes of the current discussion, the project and BOINC have to be thought of as (and actually behave as) members of the same team.

Well, the team is waiting for the manager to quit telling them to walk or bunt and start hitting home runs again.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I run with a one day cache,Im also having trouble with shortys palying havoc on my GPU. Im going to drop to a 0.25 Cache and just ride out the storm.

If worst comes to worst I will set NNT and take a deep breath.

---

[/quote]

Old James

Detaching/reattaching to the project physically deletes the setiathome project folder - so all application files and configuration setting are lost. But you usually get the same HostID, and host APR etc., back again. That's the worst possible outcome, even if you remembered to back up your applications so you can put them back again.

Resetting the project does set DCF to the default 1.0000 (and, I think, in general preserves optimised applications) - but I think the behaviour varies between different versions of BOINC - best to let someone else test it first.

The other thing that resetting the project certainly does it to throw away, without reporting, all current tasks - including those completed but not yet uploaded.

The best sequence, if you're adventurous enough to try, is:

NNT - crunch all cached tasks - upload - report - backup folder contents - reset - check folder contents are still intact - allow new work.

One little Extra to that, when you reset the project, if you had any Wu's left, copy the backed up Wu files back to your project folder before re-enabling work fetch, it'll save you having to download the Wu's again when they get resent,

Claggy

Is this the record ?
A predicted time of 591 hours for a VLAR CPU unit (normal crunching time around 100 minutes). :-S

T.A.