Thanks, Grant. As it happens, I've got all 4 crunchers on 7.6.22 at this point. Should have included that info.

Wouldn't 7.6.6 be more recent than 7.6.22???

---

Grant
Darwin NT

Any thoughts?

From memory it relates to the BOINC Manager expecting things to be done in a certain time, and they're not, so the error results.

It was suggested I upgrade BOINC, so I upgraded to v7.6.6 (I think that was the version that got the work around for that particular issue) and I haven't seen that error message since; whereas I used to get it every few weeks or so.

Thanks, Grant. As it happens, I've got all 4 crunchers on 7.6.22 at this point. Should have included that info.

Ok, nothing to do with the installer - can you open a dedicated thread please?

finish file present too long is one of those elusive ones that nobody really ever mamnged to establish the root cause.but since you manage system probelms lets start from there.

dedicated thread please.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Thanks, Grant. As it happens, I've got all 4 crunchers on 7.6.22 at this point. Should have included that info.

Wouldn't 7.6.6 be more recent than 7.6.22???

nope. 22>6 ;) you might want to read it as 7.6.06

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Thanks, Grant. As it happens, I've got all 4 crunchers on 7.6.22 at this point. Should have included that info.

Wouldn't 7.6.6 be more recent than 7.6.22???

nope. 22>6 ;) you might want to read it as 7.6.06

It would make much more sense if they did number things that way.
for me 7.6.6 = 07.60.60
7.6.22 = 07.60.22
.60>.22
Well, it used to be.


EDIT, maybe the work around that was put in one of the earlier versions got dropped for the current version?

---

Grant
Darwin NT

Thanks, Grant. As it happens, I've got all 4 crunchers on 7.6.22 at this point. Should have included that info.

Wouldn't 7.6.6 be more recent than 7.6.22???

Nope.

---

dedicated thread please.

Will do. Thanks ...

---

EDIT, maybe the work around that was put in one of the earlier versions got dropped for the current version?

The reference to a fix being included in version 7.(0)6.(0)6 was for a slightly different problem - Stderr Truncations - and I see a familiar name signing off that thread. I have no indication of a reversion on that code.

At the same time, Rom Walton put an equivalent fix into the BOINC API (the library code that all project science applications include), so the stderr problem shouldn't be reliant on a particular BOINC client version.

Jimbocous's problems seems to be happening with the x41zi cuda50 application. Unfortunately, Jason maintains his own forked version of the API library, which is still reporting version 6.2.18 (although I know it's moved on a long, long, way since then). So I don't know if that particular fix was imported into his version. Maybe he can confirm in the new thread.

Yeah, since my variant bypasses the core issues (doesn't kill threads holding buffers being written, and doesn't write a lot) you're problably looking at some system maintenance/update rather than a Boinc client or app specific problem. Naturally with any underlying issue, one or another application could be more sensitive than others. I'd Appreciate to dig deeper as per my post in the other thread, so as to completely understand what might be going on with that system (including what else might be running)

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

EDIT, maybe the work around that was put in one of the earlier versions got dropped for the current version?

The reference to a fix being included in version 7.(0)6.(0)6 was for a slightly different problem - Stderr Truncations - and I see a familiar name signing off that thread. I have no indication of a reversion on that code.

Damn.
I am losing my mind.

---

Grant
Darwin NT

Download of v0.44 is not available on link! :(

---

non-profit org. Play4Life in Zagreb, Croatia, EU

Download of v0.44 is not available on link! :(

As I said yesterday, v0.44 can't really be recommended any more, because the application version numbers are out of date. v0.45 is in preparation, but the new applications are still going through a process of testing and revision. So we're between versions at the moment.

Having said that, I don't know which link you're talking about, but the Release announcement listed two alternative mirror sites for v0.44, and v0.45 Beta3 (soon to be Beta4) is publicly available via this board.

Hello Richard,

...and v0.45 Beta3 (soon to be Beta4) is publicly available via this board.

Any update available wrt ETA for Beta4, and what's to be expected in it?

Cheers,
Rob :-}

---