Idle: ...Didn't the credit system recently change at Einstein as well?

Twice Einstein reduced the WU credit it was granting in order to get "parity" with Rosetta and other projects, but that was over the summer time frame iirc. I'm not aware of any changes in recent weeks. It's the reduction in Rosetta's RAC I'm concerned with especially since I increased the resource share and yet my RAC fell even further. Didn't the RAC start dropping when newer protein studies were released in the last month or so? On a positive note I haven't had any ghosts for many weeks; I used to get them frequently resulting in me taking a long hiatus from Rosetta.

I'm of the opinion that until Rom puts in on the download page as "recommended", it is still alpha. He even posted to the Alpha list that he wanted us testers to have a go at it before he releases it as "recommended". It was a good call too, since it had installer issues(which have been corrected now). LOL

It's just my opinion.

When they moved to Major version 5, they implemented the new three number version system (one that hasn't strictly been followed, IMO). Using 5.x.x as the example, the first number 5 means it's "major version 5", the second number is the "minor version"number. If it's ODD it's Alpha, if it's EVEN it's a recommended version. The third number is the "release number".

So, yes, it says 5.8.0, so it's slated to be a recommended version, it's just not supplanted 5.4.11 yet.

yeah I posted about that install problem :-D

but like I said slated to be the recommended version = release candidate (windows world) it does not mean it has gone gold/final.

I know they are called alpha testers, but how many of the alpha's are testing 5.9.x series out ?
To me when he releases it to testing it is well past the alpha stage and in the beta stage.
(though we could go on and on again about terminology and how boinc calls it compared to other people and different boinc projects call it.)

---

Team mauisun.org

[...]Rosetta has caused BOINC client to terminate (as described in this thread) during this same time period.

Actually, it's not just Rosetta. I have several machines that are not running Rosetta that have experienced the problem several times each. So either other projects have the same problem with their applications, or the problem is with TCP/IP (always happens during up/download), or the problem is purely a BOINC problem.

I emailed some error logs to Rom, but haven't heard anything back.

I never had boinc client terminate with any project except Rosetta until last night. Einstein was "Project Down" for some reason. When it came online it attempted to "Resend Lost Results" accompanied by 2 input data files. Boinc seemed to choke on the 2 large data files and the client terminated. Lost another 4 hours before I discovered it.

I recently upgraded my 6 macs to 5.8.0. After about 4 days, I experienced the same problem on a Mac for the first time ever. Coincidence?

---

Reno, NV
Team: SETI.USA

I recently upgraded my 6 macs to 5.8.0. After about 4 days, I experienced the same problem on a Mac for the first time ever. Coincidence?

I've never had a problem with my mac. I'll upgrade to 5.8.0 and we'll see ;)

Does anyone have any news on the subject of boinc dropping communications with the client? I know that people submitted evidence for review. It happened to me again today and continues to happen if I allow new tasks to be downloaded as needed. So I fill up my cache and don't allow new tasks on any of my projects until I can sit and monitor the downloads; if communications are dropped I can immediately restart boinc. Communications for me always seem to get lost when there is a file over 2MB involved; the larger the file the more prone I seem to be to losing the client. Baby sitting this situation is tiresome.

What's the latest on this? One of the guys on my team is having the same prob and i'm not sure what to suggest!

I guess it must be a BOINC issue if it's affecting Leiden and other projects too?

cheers
Danny

---

The finger points at the libCURL library at the moment. This was updated to the latest version in 5.8.3, but it's too early to say if this is the fix yet - I've had it running on some hosts for a couple of days so far without problems though.

---

The finger points at the libCURL library at the moment. This was updated to the latest version in 5.8.3, but it's too early to say if this is the fix yet - I've had it running on some hosts for a couple of days so far without problems though.

libCURL was only updated to see if it would fix the depspid changing IP problem, (personally depspid should use a no-ip/dyndns type service as they switch the IP address much quicker...)

---

Team mauisun.org