Austin S. Hemmelgarn
Austin S. Hemmelgarn
Actually, this is resolved now.
On further inspection, it appears this is an issue with the dashboard code specifically, albeit probably at least partially caused by the design of the REST API. Manually querying `/api/v1/charts`...
We probably also want `vfork()` and `clone()` for this as well.
There's not really any reliable way to do this. On pretty much every platform BOINC runs on, you have no guarantee that you can even retrieve the fan speed, let...
And unlike fan speed, you actually have some reasonable level of control over CPU temperature (and that has practical applications _beyond_ limiting fan speed, for example the battery temperature checking...
Being able to limit computation based on temperature in general would be nice. It's not going to solve this issue though, because how temperature correlates to fan speed, and then...
That becomes problematic when dealing with clients with dynamic addresses, you'd need a system with a static address in the network for such a scheme to work reliably, because there's...
To retain feature parity though, there would need to be an option to run independently of the default bootstrap servers and DHT network. Otherwise, this is functionally a regression for...
Adding on to @masgo's idea: Given a situation with three nodes A, B, and C, it's likely that all three want to share data directly. If B has a fixed...
@calmh Also, your argument against using PEX could be applied to a DHT setup as well: All my devices care about is how to talk to the rest of my...