Version 7.16.11 of the BOINC client software has been released for Mac OS and Windows. Release notes are here.

---

Hi,

the macos version is now signed by "Charlie Fenton (R2TC2Z4282)" instead of "The University California Berkeley (ZVCAM664D8)". Is that correct?

Regards
Listen

I forwarded that to the BOINC Dev email list and the developer (Charlie Fenton)

---

Yes, I have built and code signed every version of BOINC ever released for the Mac except for 7.16.6. BOINC version 7.16.6 was the only Mac build done by David Anderson, who used the U.C. Berkeley developer account.

---

Charlie Fenton
BOINC / SETI@home Macintosh & Windows Programmer

Thank you for the update - and thank you for your work :-)

There's RISC-V client 7.16.11 too, and a manager, via OpenSuSE Ports Tumbleweed for riscv64.

---

Since updating to 7.16.11 I have seen, on several occasions, messages like this on the "Notices" tab.

>>>
Rosetta@home: Notice from server
Rosetta needs 278.61MB more disk space. You currently have 1438.00 MB available and it needs 1716.61 MB.
>>>

This is simply an example, I have seen similar messages reported from several projects, ie. this is not a specific Rosetta issue. The hardware and OS, (Windows 8.1 x64), is unchanged. A restart corrects the problem... for a while. Resource leak perhaps?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Since updating to 7.16.11 I have seen, on several occasions, messages like this on the "Notices" tab.

>>>
Rosetta@home: Notice from server
Rosetta needs 278.61MB more disk space. You currently have 1438.00 MB available and it needs 1716.61 MB.
>>>

This is simply an example, I have seen similar messages reported from several projects, ie. this is not a specific Rosetta issue. The hardware and OS, (Windows 8.1 x64), is unchanged. A restart corrects the problem... for a while. Resource leak perhaps?

Sounds like you need to allow BOINC some more space in computing preferences. What do you see in the disk tab in the manager? For example on my new machine I have
used by BOINC: 23.8GB
free, available to BOINC: 119.95GB
free, not available to BOINC 19.95GB
used by other programs:69.92GB

Computing Preferences for the disk has a tick in the box "Leave at least 5 GB free" the "5" is a value I have entered. Belarc says there is well more than that available. My thought is that something is creating a work space on the SSD but not deallocating or deleting it when it is finished. It is a little odd that a restart seems to "fix" the issue.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

It is a little odd that a restart seems to "fix" the issue.

No, because a reboot will unload all (virtual/disk) memory, which then after a time fills up again. The disk preferences don't just exist of "Leave at least N GB free", they also comprise "Use no more than N GB" and "Use no more than N% of total" (disk space). What are those numbers then and what is the size of the disk BOINC its data directory is on?

---

>>> No,

Yes, that is true.

They are not ticked and blank. It is a 128GB SSD. I've deleted some "junk" from downloads, old installers and such like.

I'll keep an eye on it.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

They are not ticked and blank.

Which doesn't mean they're not used. They're used with the default values 100 and 0.000. You can check in global_prefs_override.xml that those values are correct, for <disk_max_used_pct> and <disk_min_free_pct>

<disk_max_used_pct>100.000000</disk_max_used_pct>

As you said.

<disk_min_free_gb>5.000000</disk_min_free_gb>

There is no value in the file for <disk_min_free_pct>

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

You guys REALLY need to update the Linux x64 shell install file, and even the 32-bit version. It's getting kinda embarrassing. People that want to crunch on Linux have to go their software repository instead of downloading the latest version here.

A disclaimer of "This may not be the latest version" doesn't cut it in 2020.

People that want to crunch on Linux have to go their software repository instead of downloading the latest version here.

That's because that's the new policy. The package maintainers add the newer/newest versions, the BOINC release manager(s) no longer do. Besides, I don't even think we have a release manager for BOINC on Linux.

It's done this way that the package that's built has all the correct libraries for that built for that Linux distribution, instead of BOINC building a version that's broken on 3/4s of the distros out here.

People that want to crunch on Linux have to go their software repository instead of downloading the latest version here.

That's because that's the new policy. The package maintainers add the newer/newest versions, the BOINC release manager(s) no longer do. Besides, I don't even think we have a release manager for BOINC on Linux.

It's done this way that the package that's built has all the correct libraries for that built for that Linux distribution, instead of BOINC building a version that's broken on 3/4s of the distros out here.

Has something changed to make it broken on 3/4 of the distros? For many years I crunched using Mandrake, then Mandriva and went through a few more distros as things changed before going down the Ubuntu route which I have now stuck with for several years. The ones that I could just untar and then launch with ./run_manager always worked for me with no problems on all the distros I have used. The only time I have had something break is after doing the version upgrade of Ubuntu from 19.10 to 20.04 and while on both machines that was having rolled my own in neither case did going to the one from the repository fix things.

One machine has been replaced so now has a clean install on it, the other will get a clean install when all the work it is still running is finished.

Has something changed to make it broken on 3/4 of the distros?

That was a guestimation of mine. The times BOINC did release a new version we did notice an increase in users with other than Ubuntu (style) distros having a hard time getting that BOINC version to work, which is probably still true to this day. Therefore it's better that the package maintainers provide an updated BOINC via their repositories, that way you know for sure it's been built and tested with the (updated/outdated) libraries of that distro.

That was a guestimation of mine. The times BOINC did release a new version we did notice an increase in users with other than Ubuntu (style) distros having a hard time getting that BOINC version to work, which is probably still true to this day. Therefore it's better that the package maintainers provide an updated BOINC via their repositories, that way you know for sure it's been built and tested with the (updated/outdated) libraries of that distro.

Makes me suspect that whatever changed must have been after I switched to Ubuntu given that I did quite a lot of distro hopping prior to settling down again.