Edit Package boinc-client

The BOINC client core

The Berkeley Open Infrastructure for Network Computing (BOINC) is an open-
source software platform which supports distributed computing, primarily in
the form of "volunteer" computing and "desktop Grid" computing. It is well
suited for problems which are often described as "trivially parallel". BOINC
is the underlying software used by projects such as SETI@home, Einstein@Home,
ClimatePrediciton.net, the World Community Grid, and many other distributed
computing projects.

This package installs the BOINC client software, which will allow your
computer to participate in one or more BOINC projects, using your spare
computer time to search for cures for diseases, model protein folding, study
global warming, discover sources of gravitational waves, and many other types
of scientific and mathematical research.

Source Files
Filename Size Changed
7.20.2.tar.gz 0046555666 44.4 MB 4 months
README.SUSE 0000005314 5.19 KB over 8 years
boinc-client-rpmlintrc 0000000039 39 Bytes over 8 years
boinc-client.changes 0000025984 25.4 KB 4 months
boinc-client.init 0000006819 6.66 KB over 10 years
boinc-client.service 0000000842 842 Bytes almost 5 years
boinc-client.spec 0000011288 11 KB 4 months
boinc-docbook2x.patch 0000000905 905 Bytes about 5 years
boinc-logrotate 0000000480 480 Bytes almost 11 years
boinc-manager 0000000221 221 Bytes almost 6 years
build-client-scripts.patch 0000000250 250 Bytes over 4 years
libboinc-shared.patch 0000007031 6.87 KB 6 months
sysconfig.boinc-client 0000001510 1.47 KB almost 6 years
xlocale.patch 0000000470 470 Bytes over 4 years
Comments 7

Linus Kardell's avatar

LinAGKar wrote over 2 years ago

Why did you break idle detection in this?

Jan Engelhardt's avatar

jengelh wrote over 2 years ago

What kinda question is that... if you have a bug report to make, please do so upstream at https://github.com/BOINC/boinc .

Linus Kardell's avatar

LinAGKar wrote over 1 year ago

No, this is something that was done deliberately in the OpenSUSE packages, it works fine in the upstream version.

Aaron Puchert's avatar

aaronpuchert wrote over 2 years ago

Idle detection was always broken. If you're running BOINC as a separate service, as openSUSE does it, it doesn't have access to your X server, and it will do nothing more than spam your logs (https://github.com/BOINC/boinc/issues/2256). Needless to say that it doesn't work on Wayland at all. That's why I proposed to disable it entirely in sr#626119.

Solving this doesn't seem trivial, which is why the upstream bug is almost three years old. My recommendation would be to go with exclusive applications or limits on CPU or memory usage for now.

Alternatively, solve the issue by finding a way to detect idleness without access to an X session.

Linus Kardell's avatar

LinAGKar wrote over 1 year ago

It does work just fine, as long as you give Boinc access to the X server, except here the functionality has been patched out to very little benefit, with no alternative given. So now it will just refuse to work for no apparent reason even with the workarounds that work for the upstream version, and used to work with this version, leading to confusion. And you don't even mention this in the description. How about you find a way, if you're gonna patch out core functionality that works perfectly fine. As for limits, they do not work for GPU usage.

Aaron Puchert's avatar

aaronpuchert wrote over 1 year ago

You can certainly give BOINC access to the X server, but we're talking about a service that downloads random binaries from not-really-trusted sources and runs them, so I wouldn't recommend this.

Removing the "functionality" provides the benefit of not spamming the system log to the point of rendering it unusable. Which is something that people care about. Also people care about a computation daemon not depending on X libraries.

The biggest problem about the existing idle detection is that it's architecturally wrong. The right architecture is a process running under the X or Wayland session and its user that signals to BOINC from the outside if it should do work or not. Gladly people are working on that. But I think you know that, since you commented on the issue.

Could we reenable idle detection in its current sorry state? Yes, but it's fundamentally at odds with users who want more security, see e.g. #4105. At some point we will run into conflicts between strengthening the sandboxing of the service and the current idle detection. If that were a fundamental conflict I would be happy to discuss it, but since a proper design would both allow idle detection and be secure that discussion doesn't make sense.

If you want this to work, my best advice is to check in with Germano about the state of his efforts or help get them in yourself. Resurrecting this broken mess isn't going to help anyone in the long run.

Linus Kardell's avatar

LinAGKar wrote over 1 year ago

Not saying it's ideal in the long run. It should certainly be replaced as soon as possible. But until then, this is the only option. So I guess until then I'll keep compiling it on my own.

openSUSE Build Service is sponsored by