Jord: adding missing links

2016-09-05T14:06:54Z

adding missing links

Jord: adding Installing BOINC on Fedora from user manual wiki

2016-09-05T14:04:15Z

adding Installing BOINC on Fedora from user manual wiki

New page

==Basic installation==
Installs BOINC Client as a daemon (autostarts the BOINC client at boot time) and puts a BOINC Manager icon on the applications menu.
To install it, open a terminal, enter:
su -c 'yum install boinc-client boinc-manager'
Give the root password when prompted and be patient while the BOINC package downloads and installs.

Alternately, fetch the <code>boinc-client</code> and <code>boinc-manager</code> rpm packages (using for instance <code>rpm.pbone.net</code>), and open them with the Package Installer. You'll be prompted for the root password as appropriate.

Optional: if you want to have Linux auto-start boinc-client daemon at boot time, enter '''<code>/sbin/chkconfig boinc-client on</code>''' (in Fedora 16), or '''<code>systemctl enable boinc-client.service</code>''' (in Fedora 17). (See [[Stop or start BOINC daemon after boot]] page for helpful commands for managing the daemon)

==What the installer does==
# Creates the daemon script. In F16: '''<code>/etc/init.d/boinc-client</code>'''. In F17: '''<code>/usr/lib/systemd/system/boinc-client.service</code>'''.
# Places the BOINC binaries (<code>boinc_client</code>, <code>boinc_cmd</code> and <code>boincmgr</code>) in <code>/usr/bin/</code>.
# Creates <code>/var/lib/boinc/</code> for BOINC data files and the <code>slots</code> and <code>projects</code> directories.
# Names the daemon <code>boinc-client</code>.
# Creates a user named <code>boinc</code>. For security, <code>boinc</code> owns the BOINC data directory (<code>/var/lib/boinc/</code>) and all the data files and sub-directories it creates in the data directory.

==Verify the installation==
# If you elected to have Linux start the daemon at boot time (see step 3 in section Basic installation), logout and reboot Linux now and login under your normal user account.
# If you elected to not have Linux start the daemon at boot time, start the daemon manually with in F16 <code>/sbin/service boinc-client start</code>, in F17 <code>systemctl start boinc-client.service</code>
# Open a terminal and enter <code>ps aux | grep boinc</code> to print a partial list of running processes. You should see <code>boinc_client --daemon</code> in that list; if not, then something went wrong in the steps above. Or alternatively in F17 <code>systemctl status boinc-client.service</code> will display the status of the boinc-client service. Or <code>pgrep -l boinc</code> will display the procid and daemon name, that is "2298 boinc_client".

==Set up your accounts==

To use the GUI to set up your accounts and monitor progress:
* Start <code>boincmgr</code> on the command line or select <code>Applications -> System Tools -> Boinc Manager</code> from the GNOME menu.
* Select <code>Advanced -> Select computer...</code> from the Boinc Manager menu.
* Put <code>localhost</code> in for "Host name" and the contents of <code>/var/lib/boinc/gui_rpc_auth.cfg</code> for "Password" and hit "OK".

If you do only the basic installation as described above, BOINC manager will not be able to automatically connect to the client. To connect the client you will be required to give the GUI RPC password every time you start BOINC manager. That is not a bug, it is a security feature to prevent other users from using the manager to manipulate the client, change your projects, etc.

If you don't want to put the password every time you run the BOINC manager, you can:

# disable the password ['''not recommended'''] To make the GUI passwordless, do '''<code>echo > /var/lib/boinc/gui_rpc_auth.cfg</code>''' (which replaces the contents of the file with a newline) and then restart boinc-client (with e.g. in F16: '''<code>/sbin/service boinc-client restart</code>''', in F17: '''<code>systemctl restart boinc-client.service</code>''').
# '''use the recommended procedure''' Boinc (the user named <code>boinc</code>) owns <code>/var/lib/boinc/</code> and all the files and directories in it, so you will not be able to edit those files easily from your regular user account. The steps below add your username to the <code>boinc</code> group and adjust some permissions so that BOINC manager will automatically connect to BOINC client whenever you start the manager from your regular Linux user account. Also, you will be able to edit files in the BOINC directory without becoming <code>root</code>. As you type in each command below, substitute your Linux username wherever you see <code>username</code>. Enter the following commands in a terminal, as <code>root</code>:
## <code>/usr/sbin/usermod -G boinc -a username</code>
## <code>chmod g+rw /var/lib/boinc</code>
## <code>chmod g+rw /var/lib/boinc/*.*</code>
## <code>ln -s /var/lib/boinc/gui_rpc_auth.cfg /home/username/gui_rpc_auth.cfg</code>
## Finally, '''logout and login again''' so that your new group membership takes effect.

==Cuda==
If you want to use Cuda, install it as described here: https://fedoraproject.org/wiki/Cuda , and install '''xorg-x11-drv-nvidia-libs''' (to avoid <code>libcuda.so.1: cannot open shared object file</code> error message) with this:
su -c 'yum install xorg-x11-drv-nvidia-libs'
You will also need to disable SELinux:
su -c 'setenforce 0'

==Optional setup hints==
''For more information about configuring BOINC in Linux, see [[Linux file permissions]].''

''Since Fedora such as version 13 has a firewall switched on by default it is necessary to configure exceptions allowing BOINC to communicate via the localhost IP 127.0.0.1 and port 31416.''

==Uninstallation==
In a terminal, enter:
su -c 'yum remove boinc-client boinc-manager'

==Known problems==

<code>boinc-client</code> sometimes has problems connecting to the network, if the network connection comes up after the client has already started. This is a known BOINC bug, which is filed as [http://boinc.berkeley.edu/trac/ticket/707 #707].

In the meantime, you can fix this by restarting <code>boinc-client</code>. On the command line, as <code>root</code>, do <code>/sbin/service boinc-client restart</code>. Alternately, from the GNOME menu, you can choose <code>System -> Administration -> Services</code> and then stop and start the <code>boinc-client</code> service.

[[Category:Linux Installation]]

@@ Line 7: / Line 7: @@
 Alternately, fetch the <code>boinc-client</code> and <code>boinc-manager</code> rpm packages (using for instance <code>rpm.pbone.net</code>), and open them with the Package Installer. You'll be prompted for the root password as appropriate.
-Optional: if you want to have Linux auto-start boinc-client daemon at boot time, enter '''<code>/sbin/chkconfig boinc-client on</code>''' (in Fedora 16), or '''<code>systemctl enable boinc-client.service</code>''' (in Fedora 17). (See [[Stop or start BOINC daemon after boot]] page for helpful commands for managing the daemon)
+Optional: if you want to have Linux auto-start boinc-client daemon at boot time, enter '''<code>/sbin/chkconfig boinc-client on</code>''' (in Fedora 16), or '''<code>systemctl enable boinc-client.service</code>''' (in Fedora 17). (See [http://boinc.berkeley.edu/wiki/Stop_or_start_BOINC_daemon_after_boot Stop or start BOINC daemon after boot] in the BOINC User Manual Wiki for helpful commands for managing the daemon).
 ==What the installer does==
@@ Line 49: / Line 49: @@
 ==Optional setup hints==
-''For more information about configuring BOINC in Linux, see [[Linux file permissions]].''
+''For more information about configuring BOINC in Linux, see [http://boinc.berkeley.edu/wiki/Linux_file_permissions Linux file permissions] in the BOINC User Manual Wiki.''
 ''Since Fedora such as version 13 has a firewall switched on by default it is necessary to configure exceptions allowing BOINC to communicate via the localhost IP 127.0.0.1 and port 31416.''

Installing BOINC on Fedora - Revision history

Jord: adding missing links

Jord: adding Installing BOINC on Fedora from user manual wiki