BOINC website: "Use the idle time on your computer (Windows, Mac, or Linux) to cure diseases, study global warming, discover pulsars, and do many other types of scientific research. It's safe, secure, and easy."
Wikipedia: "The Berkeley Open Infrastructure for Network Computing (BOINC) is a non-commercial middleware system for volunteer and grid computing. It was originally developed to support the SETI@home project before it became useful as a platform for other distributed applications in areas as diverse as mathematics, medicine, molecular biology, climatology, and astrophysics. The intent of BOINC is to make it possible for researchers to tap into the enormous processing power of personal computers around the world."
BOINC is installed as a daemon and for security reasons will be run under the newly created boinc user. We will add ourself to the boinc group and create a link to the password file so that we can manage it via the GUI.
Install BOINC via pacman:
# pacman -S boinc
You can control boinc service under systemd.
To start boinc:
# systemctl start boinc
To enable boinc service:
# systemctl enable boinc
BOINC runs as a daemon, to run at start up add it to the daemons section in
DAEMONS=(... boinc ...)
Add your user to the boinc group. You will need to log out and in again for it to take effect.
# gpasswd -a username boinc
If you want, you can easily check if you are now part of the boinc group by using the groups command:
Start the BOINC daemon:
# /etc/rc.d/boinc start
Check if BOINC is running:
$ ps aux | grep boinc
If you're planning to run BOINC on a headless server, and would like to avoid installing wkWidgets and GTK for a GUI that you won't use anyway, consider installing AUR.AUR from the
BOINC via the GUI
By default, a password is created in
/var/lib/boinc/gui_rpc_auth.cfg for connecting to the daemon. To simplify connection of the GUI to the daemon, cd to your home directory, create a link to the file, and change permissions to allow read access to boinc group members.
$ cd $ ln -s /var/lib/boinc/gui_rpc_auth.cfg gui_rpc_auth.cfg # chmod 640 gui_rpc_auth.cfg
If you prefer a different password, or none at all, you can edit
/var/lib/boinc/gui_rpc_auth.cfg. Then restart BOINC daemon.
If you do not like the idea of having this file in your home directory, there is an alternative approach. BOINC Manager will also look for a readable gui_rpc_auth.cfg file in the current working directory. If you make the file readable by the boinc group and ensure that the manager is run with
/var/lib/boinc as the working directory, you should find that the client connects to the daemon automatically, as desired. This can usually be achieved via the menu editor in your desktop environment of choice.
To start the GUI, use the boincmgr command
BOINC should now take you through the process of attaching to a project. NB, some projects will let you create an account remotely via the GUI while some may require you to first create an account via their website. You can attach to multiple projects if you have the resources (disk space, time, CPU power). Do this via menu option Tools / Attach to project.
If BOINC did not ask you to connect to a project, then make sure you are connected to the daemon. Go to menu option Advanced / Select computer, choose your machine's name and enter the password. (To avoid this, make sure the above steps regarding gui_rpc_auth.cfg have been done.)
Projects using GPU
If you want to use your GPU, you need the proprietary nvidia or amd drivers. For ATI/AMD Cards you also need Catalyst driver for stock kernel which you can get from AUR. For Nvidia, you also need the package located in extra.
In addition, the boinc user should be in the video group:
# gpasswd -a boinc video
The boinc user also needs to have access to your X session. Use this command to accomplish this:
You may want to add that to a startup script.
NB, BOINC places log files in
Considerations when choosing a project
Projects have different minimum hardware requirements (CPU, disk space), and different times to taken to run each work unit. If you do not finish a work unit before the deadline it will sent out to someone else, but it is better to look around to see what projects suit your machine and your uptime patterns to avoid this happening.
Also, if it is important to you, check if the project makes the data and results publicly available.
Running on Arch64
Some projects provide only 32bit applications which may require 32bit libraries to run work units or show graphics. You will find most of these libraries in the [multilib] repository.
- To run WUs (e.g. Climateprediction)
- To show graphics (e.g. Several projects of WCG, Climateprediction)
- , , , , AUR (AUR), and
If you get this error :
and the Work Unit does not start, you should restart the BOINC daemon :
# /etc/rc.d/boinc restart
This will happen if the BOINC daemon starts before the an X session is fully initialized. Generally, if the daemon is set to start in the background in rc.conf, this doesn't happen, but it does sometimes beat the display manager. If, however, no display manager is set to load on boot, the daemon will always have to be restarted after X initialization for the GPU to be recognized.
Running boinc in laptops
If you run Boinc in your laptop with ondemand governor, the CPUs will be kept always at maximum frequencies and thus (over)heating them and decreasing battery duration. The best way to fix it is to tell the governor not to rise frequency for boinc:
echo 1 >/sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
This may be added to /etc/rc.local (if you don't use native initscripts and not systemd).