Since then it has run up more than 37 hours. I propose to let it run another day or so and see what happens.

Looks like your preferred runtime is 3hrs. The watchdog should have killed that task some time ago. You've already exited and restarted BOINC and it did not complete the task, so I suggest you abort it. Sorry.

Also, please join the Linux problems discussion

---

Rosetta Moderator: Mod.Sense

Since then it has run up more than 37 hours. I propose to let it run another day or so and see what happens.

Looks like your preferred runtime is 3hrs. The watchdog should have killed that task some time ago. You've already exited and restarted BOINC and it did not complete the task, so I suggest you abort it. Sorry.

Also, please join the Linux problems discussion

Note that when I exited BOINC it did not manage to kill the rosetta processes. I seem to remember that this is always the case. Could there be a problem in either the BOINC client, or the rosetta application that makes this happen?

I do not care what my preferred run time is. Would it make sense for me to increase it?

---

Note that when I exited BOINC it did not manage to kill the rosetta processes. I seem to remember that this is always the case. Could there be a problem in either the BOINC client, or the rosetta application that makes this happen?

Yes, there could be a problem. Exploring that possibility is the purpose of the other thread and why I asked you to contribute your symptoms and observations there as well.

I do not care what my preferred run time is. Would it make sense for me to increase it?

I mentioned it only because one of the watchdog's criteria for ending a task is when it has run for 4 times longer then your preferred runtime. So if you had recently changed your runtime to 24hrs for example, then I wouldn't have expected the watchdog to kick in yet. The watchdog not ending the task is another symptom we need to study in the Linux preemption thread.

No, I am not suggesting a change to your preference. Some Linux users feel a shorter runtime tends to improve their success rate.

---

Rosetta Moderator: Mod.Sense

I have the same issue with two work units on my 64bit ubuntu 7.04 distro.
The two tasks in question both start with STM0082_BOINC_MFR_ABRELAX_PICKED_2175
I've tried restarting my system, and suspending-resuming tasks. Boinc has already given me more projects to work on, and I've started workin on those instead. I've already spent 9 hours of cpu time on each of the 'broken' ones, and i should have only had to spend half of that.