Do you run them on virtualbox or natively on linux?

I only run native Linuc WUs and never use virtualbox.

You got LHC to run natively? Their instructions are in Greek. I can't get their native stuff to work and I can't get their Squid to work either, why can't they make their tasks share big datasets instead of downloading them 24 times for 24 cores?

I've only found two coins which aren't scams, Gridcoin and Curecoin. They give you coins for work you're already doing in Boinc and Folding@Home, not ask you to run mindless calculations for other people.

I found it was absolutely trivial to setup and run DNX. The early miners had bugs.

The problem is the virus inside it.

GRC and CURE are scams too. All supply and no demand.

How can it be a scam if I end up with a small amount of cash instead of no cash for running Boinc?

Nobody actually needs cryptocurrency

It was a nice idea, we could have got away from banks and governments, but they lack the ability to remain stable. I don't want to have 50 grand of money which might be 1 grand tomorrow.

Someone should figure out a way to pay workers using real money so they cover their electric bills. Somebody will but crypto is not the answer.

Solar is the answer, stop buying power off the grid. 10x cheaper....

Einstein doesn't freeze my computers. Boinc removes tasks if the memory is too full.

Einstein does not freeze my computers either.
I do not know if Boinc removes tasks if memory is too full, whatever that means. I know Linux can do that, but I have never had it happen and I have been running Linux since about 1998 (Red Hat not enterprise Linux 5 to begin with).
I am currently running Red Hat Enterprise Linux release 8.8 (Ootpa)

---

I do not know if Boinc removes tasks if memory is too full, whatever that means.

Boinc is set to use x% of RAM. If that is exceeded, it will suspend a task. Just as it won't start one if there isn't room. You will then notice only 6 tasks running on an 8 core computer for example.

I know Linux can do that, but I have never had it happen and I have been running Linux since about 1998 (Red Hat not enterprise Linux 5 to begin with).
I am currently running Red Hat Enterprise Linux release 8.8 (Ootpa)

I would hope an OS would never do that. The application could be important and have unsaved work. Or did you mean swap to disk?

I know Linux can do that, but I have never had it happen and I have been running Linux since about 1998 (Red Hat not enterprise Linux 5 to begin with).
I am currently running Red Hat Enterprise Linux release 8.8 (Ootpa)

I would hope an OS would never do that. The application could be important and have unsaved work. Or did you mean swap to disk?

I do not mean swap to disk.

https://neo4j.com/developer/kb/linux-out-of-memory-killer/

This one is probably better:

https://rakeshjain-devops.medium.com/linux-out-of-memory-killer-31e477a45759

---

I do not mean swap to disk.

https://neo4j.com/developer/kb/linux-out-of-memory-killer/

Wow, that's pure insanity, but being Linux it doesn't surprise me. Swapping would be more sensible.

Wow, that's pure insanity, but being Linux it doesn't surprise me. Swapping would be more sensible.

I would not blame Linux. And when things get so bad as to run the system out of memory, swapping may not be possible: buffers would be required to do the swap, and there is proibably no space for the needed buffers.

As I said earlier, in over 20 years of running Linux, this has never happened to me.

---

I would not blame Linux. And when things get so bad as to run the system out of memory, swapping may not be possible: buffers would be required to do the swap, and there is proibably no space for the needed buffers.

As I said earlier, in over 20 years of running Linux, this has never happened to me.

Windows swaps. Just don't let it get that bad. It's like letting your car run completely out of petrol.

I do not know if Boinc removes tasks if memory is too full, whatever that means.

Boinc is set to use x% of RAM. If that is exceeded, it will suspend a task. Just as it won't start one if there isn't room. You will then notice only 6 tasks running on an 8 core computer for example.

That's not accurate. The boinc client ignores the memory requirement of the task specified in the workunit XML when deciding whether to start it or not. It only checks the memory when the task is running. This is why we have problems with OpenIFS tasks with their Gbs requirement. If a host get multiple OIFS tasks but does not have enough RAM to run all concurrently, the client still starts them and they will crash because they run out of memory. The client doesn't check frequently enough to catch the rapid increase in RAM of the processes.

It's a known longstanding 'issue' with the boinc client and why CPDN, like LHC, have to limit the no. of tasks sent to volunteers for large memory tasks. That's the only workaround.

---

---
CPDN Visiting Scientist

Another known longstanding 'issue' is that many of us who have used BOINC for a long time have picked up bits and bobs of information that we have taken as gospel, spouted them out for years and only when someone who really knows either the BOINC code or the details of what the task code does sees us spouting them do we learn the truth! I could point to probably half a dozen things I had assumed to be the case that you have put me right on Glen, many of them, things I picked up from those who have been involved with BOINC even longer than I have!
Edit:

The boinc client ignores the memory requirement of the task specified in the workunit XML when deciding whether to start it or not. It only checks the memory when the task is running.

I assume this been raised over at git-hub though a quick search didn't find anything.

Another known longstanding 'issue' is that many of us who have used BOINC for a long time have picked up bits and bobs of information that we have taken as gospel, spouted them out for years and only when someone who really knows either the BOINC code or the details of what the task code does sees us spouting them do we learn the truth! I could point to probably half a dozen things I had assumed to be the case that you have put me right on Glen, many of them, things I picked up from those who have been involved with BOINC even longer than I have!

To be fair, I assumed the client did look at the memory of the task before starting it - because that's how it 'looks like it should work' in the client settings. Why would the memory behaviour be any different to behaviour with disk limits. It was only when investigating with OpenIFS and talking to LHC did we find out.

---

---
CPDN Visiting Scientist

I've seen it refusing to start tasks due to not enough memory. I guess that might be because it's already reached the limit, or maybe it started one then stopped it, but I'm 90% sure it looked like it was being sensible. It never overloads the computer anyway, worst case scenario, a task starts, stops, then has to start again another time.

LHC impose no limits. Any limits have to be inserted yourself in app_config. Or I guess on their webapge, but you have to make the choice and work out how many.

A heads-up that there will be a new batch for WAH2 coming out in the next week or two. This is the resend of the East Asia (Korean) batch that had a lot of problems. It's a new configuration which has been tested to behave better.

Also further ahead is another New Zealand WAH2 batch.

---

---
CPDN Visiting Scientist

Next East-Asia (eas25) batch being released now (Windows only).

Any problems, please report in new thread rather than this one. Thx.

---

---
CPDN Visiting Scientist

Collected one task on each of two machines, to see how they run. Both made a clean start, looking good so far.

Got one on my pipsqueek Windows10 machine and it has over 15 minutes on it so far. Predicting 9 days 18 hours to go.
Task 22340449
Computer 1512658

---

I'm getting a lot of resends, and I'm breaking them myself too. Looks like you haven't fixed the problem of the task going wrong if the computer is rebooted. People reboot because they want to, or because the computer crashes, or because Windows Update illegally restarts your machine which isn't their property for updates (I've tried everything, M$ keeps resetting the workarounds). How hard can it be to write proper checkpoints?

M$ keeps resetting the workarounds).

Have you tried blocking the MS domain in your router. Those I know who have done that find it works pretty well.

How hard can it be to write proper checkpoints?

Perhaps you should learn Fortran and volunterr your services?

M$ keeps resetting the workarounds).

Have you tried blocking the MS domain in your router. Those I know who have done that find it works pretty well.

But I want updates, just no reboots until I say so.

How hard can it be to write proper checkpoints?

Perhaps you should learn Fortran and volunterr your services?

I feel it's not the programming at fault, but the common sense. It writes checkpoints, presumably something daft is happening like deleting the old one before creating the new one. I see no reason even cutting the machine's power should ever cause a problem.

]I feel it's not the programming at fault, but the common sense. It writes checkpoints, presumably something daft is happening like deleting the old one before creating the new one. I see no reason even cutting the machine's power should ever cause a problem.

If it was something daft it would have been fixed ages ago. It's more subtle than that. You see no reason because you don't understand the problem or the way the models work. If I had a quid for every time you moaned about something on the forums I'd have enough money to employ someone to fix it :D .. in the meantime you'll have to wait and remember (a) these models are not designed to run on systems that can be shutdown instantly, (b) CPDN has little money for developers and the staff they do have are stretched with teaching & research as well as CPDN.