Starting today, I've been getting log messages similar to this

14.12.2005 14:21:46|climateprediction.net|Result sulphur_aiam_000490270_0 exited with zero status but no 'finished' file
14.12.2005 14:21:46|climateprediction.net|If this happens repeatedly you may need to reset the project.
14.12.2005 14:21:46|SETI@home|Result 22ap04ab.11574.32242.704834.20_2 exited with zero status but no 'finished' file
14.12.2005 14:21:46|SETI@home|If this happens repeatedly you may need to reset the project.

What's going on? Never seen this before.
Apart from this, everything seems to run smoothly.

---

Do you have "leave applications in memory when preempted" set to "no"? If so, you might try setting that to "yes". These messages happen periodically to everyone, however, and you SHOULD NOT reset the project, especially CPDN, unless you start having other problems and someone advises you that a reset is your only way out.

---

Do you have "leave applications in memory when preempted" set to "no"? If so, you might try setting that to "yes". These messages happen periodically to everyone, however, and you SHOULD NOT reset the project, especially CPDN, unless you start having other problems and someone advises you that a reset is your only way out.

I've always had it on 'yes', mainly because of CPDN. For the same reason, I'm not going to reset the project unless there's no other way to resolve this issue - all those precious CPU cycles would be in vain. ;-)
Let's hope those log msg's just so go away.

---

If in further doubt, just look here for a more complete description.

---

If you clock drifts, this is one possible cause.

There are changes in the later clients that "should" address this issue. BUt, basically, it is a non-problem ...

---

Thanks for the explanations, guys. Today, there are no more of these msg's to be seen in my log, so I guess the prob has automagically solved itself. ;-)

---

It will come and go.

With the older BOINC Clients the update of the clock would cause the BOINC Daemon and the Science Applciations getting out of step and this message was the result. The newer Clients have a different accounting mechanism and in theory this should be a thing of the past (I have NOT checked this to be true however).

---

It will come and go.

With the older BOINC Clients the update of the clock would cause the BOINC Daemon and the Science Applciations getting out of step and this message was the result. The newer Clients have a different accounting mechanism and in theory this should be a thing of the past (I have NOT checked this to be true however).

Running 5.2.7 and it's still a regular part of the landscape, and still no harm whatsoever.

---

"The arc of history is long, but it bends toward Justice"