Hmm.....

My 'plan class' just says 'crunch em all'...
Cuda says 'yup'.
Kitties say 'meow'.
Seti servers say 'go'.

---

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

1) The app chosen is "none"; the 3 choices are: 6.08.cuda, 6.09.cuda23 and 6.10.cuda_fermi.

Choose 6.08.cuda and see if it will remedy the "discarding"

Also: Yes, my BOINC was again restarted after 4 hours (9:07 EST) despite having no timer set in 2.3 Rescheduler;

So you see this in the Settings tab?:

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

1) The app chosen is "none"; the 3 choices are: 6.08.cuda, 6.09.cuda23 and 6.10.cuda_fermi.

Choose 6.08.cuda and see if it will remedy the "discarding"

Also: Yes, my BOINC was again restarted after 4 hours (9:07 EST) despite having no timer set in 2.3 Rescheduler;

So you see this in the Settings tab?:

1) I will try choosing 6.08 if the behavior continues after I switch to the new case (see above).

2) yes, the Settings tab for 2.3 is the same as for 2.4; I do have "Restart after reched'g" checked, but that shouldn't matter, as there is no rescheduling being done at those times (the Log shows nothing) - unless there is a bug to be fixed...

---

In fact I tried to ask "is there a check in the box in front of Automatic mode ... or not"?

(if there is a check the timer starts to countdown immediately)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

No such check.

---

More Info:

As per above, I exited RS 2.3, so that the icon was no longer in the system tray. Then, promptly at 1:07, BOINC was restarted and the same rigmarole of throwing away "6.10" WUs (which they weren't) and then re-d/l them occurred.

I then looked in Task Manager, and what did I see?

ReSchedule.exe*32 Administrator 00 17,840K Reschedule setiathome enhanced units

(Exiting RS 2.3 doesn't warn you that it is continuing to run. I don't think the old rescheduler worked this way). So it was running still. What a bummer. I would say this is a definite bug in 2.3, and maybe in 2.4 as well (though I am NOT going to test it to find out).

---

More Info:

As per above, I exited RS 2.3, so that the icon was no longer in the system tray. Then, promptly at 1:07, BOINC was restarted and the same rigmarole of throwing away "6.10" WUs (which they weren't) and then re-d/l them occurred.

I then looked in Task Manager, and what did I see?

ReSchedule.exe*32 Administrator 00 17,840K Reschedule setiathome enhanced units

(Exiting RS 2.3 doesn't warn you that it is continuing to run. I don't think the old rescheduler worked this way). So it was running still. What a bummer. I would say this is a definite bug in 2.3, and maybe in 2.4 as well (though I am NOT going to test it to find out).

That one is not Fred's RS 2.3, his is identified as BOINC Rescheduler.

Check for the older one on your system as I think that is what is causing the problem.

---

There is another option. The BOINC client may crash for some reason and the BOINC manager can restart the BOINC client.
This gives the same behavior as you are describing.

And.... the Rescheduler should be: BOINC Rescheduler.exe. or BOINC Rescheduler64.exe for a 64 bit system.
In the TaskManager use the right mouse key to select properties. Now you can see the folder the exe is in as well a the complete name, version etc.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

That one is not Fred's RS 2.3, his is identified as BOINC Rescheduler.

Check for the older one on your system as I think that is what is causing the problem.

Well I'll be darned, but you are correct - my bad!

There is another option. The BOINC client may crash for some reason and the BOINC manager can restart the BOINC client.
This gives the same behavior as you are describing.

Not every EXACTLY 4 hours though; see above in this post. My goof!

Thank you both.

---