I'm relatively new at this but have to say I'm very disappointed.

The server passes out work units that are never received by the host, thousands upon thousands of Linux work units fail for days on end and when there is finally a so called fix most of my machines lock up necessitating recovery and lost real world data.

I'm sorry this is not in any stretch of someones imagination "Real Science" its simply fools passing themselves of as "Scientists"

I'm relatively new at this but have to say I'm very disappointed.

The server passes out work units that are never received by the host, thousands upon thousands of Linux work units fail for days on end and when there is finally a so called fix most of my machines lock up necessitating recovery and lost real world data.

I'm sorry this is not in any stretch of someones imagination "Real Science" its simply fools passing themselves of as "Scientists"

YES, thousands and thousands of Linux work units were failing for days. That's shameful.

No project has zero failed tasks, whether they report back to you that some failed or not. Furthermore, the more difficult the work, the more difficult it is to run. The more diverse the computer/GPU configuration a task can be run on means the more difficult it is to create a WU that will run to full time. Overclocking cars, even in cards called "super clocked" or otherwise that you bought overclocked can also be a factor on any GPU or CPU causing an error on a WU on any project. Even tasks that just hand out text files to analyze a simple mathematical equation can error out on a distributed project depending on any configuration or number of problems. Processor jitter (which happens more often than admitted), memory leakage from other software installed along side of the project, or internet packet loss can also contribute to anything. So when for a few days one project handing out WUs that mean so much and are this difficult to make (3-d simulated DNA involved interactions of chemicals and living cells)sends out a few WUs that are unstable or are not fully compatible with a few configurations of CPU/GPU, don't get bent out of shape. Even professionals in any field need to make small mistakes to learn how to eliminate all future ones. So just calm down, wait a few days, and try again, OR let the WUs fail and contribute more than you complain by letting the WUs teach the programmers how to better help the scientists. Your attitude is as if all life scientists have 20 years of experience with 3-d simulation of DNA structures and degrees in modern computing and everything related. Let them 'break a few eggs' so we can get breakfast, will you please?
____________
1 Corinthians 9:16 "For though I preach the gospel, I have nothing to glory of: for necessity is laid upon me; yea, woe is unto me, if I preach not the gospel!"
Ephesians 6:18-20, please ;-)
http://tbc-pa.org

There's always someone on tech forums that takes things a little too personally. You don't get brownie points for defending the developers, hell or high water.

The thousands of work units weren't failing because of any of those random errors, anyway. And the project scientists had no comment for days.

I'm a donor. I bought graphics cards out of pocket to support this project, and if there's something I don't like, I'm going to say it.

No project has zero failed tasks, whether they report back to you that some failed or not. Furthermore, the more difficult the work, the more difficult it is to run. The more diverse the computer/GPU configuration a task can be run on means the more difficult it is to create a WU that will run to full time. Overclocking cars, even in cards called "super clocked" or otherwise that you bought overclocked can also be a factor on any GPU or CPU causing an error on a WU on any project. Even tasks that just hand out text files to analyze a simple mathematical equation can error out on a distributed project depending on any configuration or number of problems. Processor jitter (which happens more often than admitted), memory leakage from other software installed along side of the project, or internet packet loss can also contribute to anything. So when for a few days one project handing out WUs that mean so much and are this difficult to make (3-d simulated DNA involved interactions of chemicals and living cells)sends out a few WUs that are unstable or are not fully compatible with a few configurations of CPU/GPU, don't get bent out of shape. Even professionals in any field need to make small mistakes to learn how to eliminate all future ones. So just calm down, wait a few days, and try again, OR let the WUs fail and contribute more than you complain by letting the WUs teach the programmers how to better help the scientists. Your attitude is as if all life scientists have 20 years of experience with 3-d simulation of DNA structures and degrees in modern computing and everything related. Let them 'break a few eggs' so we can get breakfast, will you please?

All projects have issues which get fixed. This project is no different.

This project is no different than any other University backed project in that things tend to be slow to fix during holidays.

The admin stated that the license for the code in the Linux application had expired resulting in 100% failures. This has nothing to do with overclocking. It is a configuration issue that is easy for someone with both the knowledge, access and the time to fix. The trick is finding the right "someone" when everyone is at home enjoying time with their families.

It took me a day or two to notice and move my machines to a different project. I am too stupid to figure out how to get backup projects to work reliably in Boinc for systems with multiple GPUs. Setting the priority to 0 doesn't do it. But, that's my problem and not theirs. I picked up 20 million cobbles over on another project before the license got updated. No biggie for me.