"HTPC christ # systemctl start boinc HTPC christ # systemctl status boinc ● boinc.service - BOINC Daemon Loaded: loaded (/usr/lib64/systemd/system/boinc.service; enabled) Active: active (running) since Fri 2014-10-24 15:27:15 CEST; 8s ago Main PID: 19237 (boinc_client) CGroup: /system.slice/boinc.service └─19237 /usr/bin/boinc_client --dir /var/lib/boinc --redirectio Oct 24 15:27:15 HTPC systemd[1]: Started BOINC Daemon. Oct 24 15:27:15 HTPC boinc_client[19237]: 24-Oct-2014 15:27:15 [---] No config file found - using defaults HTPC christ # systemctl status boinc ● boinc.service - BOINC Daemon Loaded: loaded (/usr/lib64/systemd/system/boinc.service; enabled) Active: failed (Result: exit-code) since Fri 2014-10-24 15:27:25 CEST; 751ms ago Process: 19237 ExecStart=/usr/bin/boinc_client --dir /var/lib/boinc --redirectio (code=exited, status=108) Main PID: 19237 (code=exited, status=108) Oct 24 15:27:15 HTPC systemd[1]: Started BOINC Daemon. Oct 24 15:27:15 HTPC boinc_client[19237]: 24-Oct-2014 15:27:15 [---] No config file found - using defaults Oct 24 15:27:25 HTPC systemd[1]: boinc.service: main process exited, code=exited, status=108/n/a Oct 24 15:27:25 HTPC systemd[1]: Unit boinc.service entered failed state. HTPC christ # journalctl -u boinc Oct 24 15:27:15 HTPC systemd[1]: Starting BOINC Daemon... Oct 24 15:27:15 HTPC systemd[1]: Started BOINC Daemon. Oct 24 15:27:15 HTPC boinc_client[19237]: 24-Oct-2014 15:27:15 [---] No config file found - using defaults Oct 24 15:27:25 HTPC systemd[1]: boinc.service: main process exited, code=exited, status=108/n/a Oct 24 15:27:25 HTPC systemd[1]: Unit boinc.service entered failed state." "ERR_FOPEN -108 1. BOINC has a problem opening or writing one or more files. One of the ways to get this error is by hiding the BOINC / BOINC Data directory and its sub-directories. Then BOINC can't find where it is running from. Solution: Do not hide your BOINC / BOINC Data directory. 2. BOINC finds that the file is open and in use by another process, or BOINC cannot write to the file. Solution: Exit BOINC completely and restart it. 3. It may happen, that when an application hangs while opening/writing to a file and then terminates abnormally (e.g. via Task Manager or even BOINC), this (formerly opened) file may stay locked even if the application is terminated (due to file locks are handled by the OS - e.g. file locks on network shares are handled by the OS for the network PC/Server - the OS needs a definite "remove this lock!" from the calling application to remove it). Solution: Restart your computer. 4. You installed BOINC as an administrator but run it as another user and didn't give that user rights to write to the BOINC or BOINC Data directory and sub-directories. The directories their read-only attributes are set. Solution: Either run BOINC as administrator, or give the user you want to run under rights to write to the BOINC /BOINC Data directory and subdirectories. "
I had to chown -R boinc:boinc /var/lib/boinc.
/var/lib/boinc is owned by boinc:boinc by default with the current ebuilds.
