Dear Ove, you have done some nice work of bug hunting already. My suggestion is to start with the IO load hypothesis and switch (in total) to a project with considerably lower demands here. You may have seen an earlier thread on reports of iostat (in package sysstat) for various projects. My suggestion would be to run einstein@home for a week or two and see if your problems are still manifesting themselves. That has only a tenth of the IO demands of say FightAids@Home on my machine. Then switch back to a particular WCG project with lower IO demands, say FAAH, and then switch from there to the Climate prediction.
We cannot solve that problem of yours this way, but we can constrain the culprit a bit more and help the bug report. For Milyway@Home we have the source code with Debian. Einstein@Home is also Open Source. If the error also happens with Einstein@Home, then to run the local compilation of Milkyway@Home with Debian seems like the next thing to try. But for the moment I do not think this is what we will see, thinking something to be straing with the WCG client. Just a hunch. Many greetings Steffen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
