chore: added resource share information for boinc

This commit is contained in:
Michele Cereda
2023-05-28 20:21:16 +02:00
parent ddfde0044f
commit 5b8cfdbc68

View File

@@ -10,11 +10,13 @@
1. [Gotchas](#gotchas)
1. [Further readings](#further-readings)
Files are located in `/var/lib/boinc` by default.
Some distribution (debian and derivate) use `/etc/boinc-client` for configuration files instead, and create links to the ones in the default location.
## TL;DR
Files are located in `/var/lib/boinc` by default.<br/>
Some distribution (debian and derivate) use `/etc/boinc-client` for configuration files instead, and create links to them in the default location.
The resource share property can be set anywhere from 0 to 1000 for each project, with 0 meaning it will not get any work from that project unless every other project you run is out of work.
```sh
# Install.
flatpak install 'edu.berkeley.BOINC'
@@ -36,6 +38,9 @@ Local control RPCs are authenticated using the GUI RPC password. This password i
A password is **required** from version FIXME, and is automatically generated if the file is not found or it is empty.
Resource share is used to help BOINC determine which projects to prioritize. The larger the number, the more it will prioritize work from that project over the other projects. It does not determine anything about how much of your CPU, GPU, etc. are used. If you want to do that, change the relative settings.<br/>
The number for resource share can be set anywhere from 0 to 1000 for each project. Setting a project's resource share to zero means it will not get any work from that project unless every other project you run is out of work.
### Remote management
All remote RPCs (both status and control) are authenticated using the GUI RPC password.
@@ -109,7 +114,7 @@ usermod --append --groups 'vboxusers' 'boinc'
## Gotchas
- it seems to work much better on debian-based distribution
- It seems to work much better on debian-based distribution than on others.
- In order to suspend computing when the computer is in use, the `boinc` user should have access to your X session so that mouse and keyboard input can be communicated to the client:
```sh