Overclock.net banner
1 - 1 of 1 Posts

·
⤷ αC
Joined
·
11,278 Posts
Discussion Starter · #1 ·
After dealing with the craziness I thought it would be a good to have it recorded for posterity. For people that don't consider GUI-less vim to be a user-friendly text-editor.
smile.gif


1. Check the installed packages. You should have boinc from Manjaro's pamac (GUI for XFCE) or pacman (commandline), do NOT install boinc-openrc. boinc-nox is the GUI-less version and is mutually exclusive from boinc
If not, install BOINC. in Terminal type

Code:

Code:
sudo pacman -S boinc
This uses commandline based pacman to install the boinc package

2. Kill boincmgr via xfce taskmanager (I find this easier than hunting down process ID)

3. Navigate to /home/ and delete gui_rpc_auth.cfg if it exists

4. In terminal type

Code:

Code:
sudo usermod -a -G boinc $(whoami)
A. add yourself to the boinc group in order for the manager to connect

Code:

Code:
sudo systemctl enable boinc.service
B. this auto starts BOINC on reboot

Code:

Code:
sudo systemctl start boinc.service
C. this starts BOINC

Code:

Code:
sudo gpasswd -a $(whoami) boinc
D. this adds your username to the user group for boinc, this is a fail-safe since the first method in step 4A may not always work for whatever reason

Code:

Code:
ln -s /var/lib/boinc/gui_rpc_auth.cfg gui_rpc_auth.cfg
symbolic link to the configuration file (GUI RPC password to be exact)

Code:

Code:
sudo chmod 640 gui_rpc_auth.cfg
E. add read permissions to the config file
some people advise using chmod 644 to solve the issue of "unable to connect to core client" (see https://bbs.archlinux.org/viewtopic.php?pid=1467343#p1467343) but that is because they did not do the step of adding to the boinc usergroup since that gives read permission to users not in the group: "6" is read/write for owner while "4" is read permissions and "0" is none (or no permissions)

Code:

Code:
sudo usermod -a -G boinc $(whoami)
sudo systemctl enable boinc.service
sudo systemctl start boinc.service
sudo gpasswd -a $(whoami) boinc
ln -s /var/lib/boinc/gui_rpc_auth.cfg gui_rpc_auth.cfg
sudo chmod 640 gui_rpc_auth.cfg

5. Reboot

6. open boincmgr and see if problem persists (in the applications menu) or via terminal (not advised since closing terminal terminates it):

Code:

Code:
boincmgr
7. If it works, proceed to use boincmgr as you do in Windows. Be sure to add yourself to the OCN team if you did not already
tongue.gif


----
FOOTNOTE
The italicized text is explanation. I'm sure most people want to know what the code does.

Pictures required...

It seems Arch-based Linux is still in its infancy for BOINC since the wcg page only lists Red Hat (inc. Fedora) / Debian-based (inc. Ubuntu)
 
1 - 1 of 1 Posts
Top