Boinc github11/28/2023 If I would cherry-pick for the new tag only commits from Android, and then you decide to do the same with commits for OSX, then we will have releases that are close (in numbers) but have significantly different functionality. I took a look at the list of commits and found no one that was done directly in 7.16.* branch without the corresponding commit in master.Įverytime cherry-pick from master is not the case, because we have 4 platforms, and like 3 independent released: Ls: cannot open directory '/var/lib/boinc-client/ ': Permission deniedĭrwxrwx-x 2 boinc boinc 4096 Feb 26 17:49 noticesĭrwxr-xr-x 2 boinc boinc 4096 Feb 26 17:49 slots rw-r-r- 1 boinc boinc 296 remote_hosts.cfg rw-rw-r- 1 boinc boinc 298 global_prefs_override.xml rw-r-r- 1 boinc boinc 0 Feb 26 17:49 stdoutgpudetect.txt rw-r-r- 1 boinc boinc 0 Feb 26 17:49 stderrgpudetect.txt Lrwxrwxrwx 1 root root 34 Feb 26 17:49 remote_hosts.cfg - > /etc/boinc-client/remote_hosts.cfgĭrwxr-xr-x 2 boinc boinc 4096 Feb 26 17:49 slots/ rw-r-r- 1 boinc boinc 0 Mar 17 22:41 lockfileĭrwxrwx-x 2 boinc boinc 4096 Feb 26 17:49 notices/ Lrwxrwxrwx 1 root root 34 Feb 26 17:49 gui_rpc_auth.cfg - > /etc/boinc-client/gui_rpc_auth.cfg Lrwxrwxrwx 1 root root 43 Feb 26 17:49 global_prefs_override.xml - > /etc/boinc-client/global_prefs_override.xml rw-r-r- 1 boinc boinc 195 Mar 17 22:40 daily_xfer_history.xml rw-r-r- 1 boinc boinc 5892 Mar 17 22:41 client_state.xml rw-r-r- 1 boinc boinc 5892 Mar 17 22:41 client_state_prev.xml Lrwxrwxrwx 1 root root 31 Feb 26 17:49 cc_config.xml - > /etc/boinc-client/cc_config.xml Lrwxrwxrwx 1 root root 34 Feb 26 17:49 ca-bundle.crt - > /etc/ssl/certs/ca-certificates.crt rw-r-r- 1 root boinc 296 remote_hosts.cfg rw-rw-r- 1 root boinc 298 global_prefs_override.xml rw-rw-r- 1 boinc boinc 356 cc_config.xml This is what I recall being the current configuration but I haven't tested in the past couple of months so things might have changed.When these steps are completed, you should see a screen to confirm that you've been successfully signed up to World Community Grid. When BOINC Manager opens, select World Community Grid from the list of BOINC projects then enter your World Community Grid username and password.ĩ. In the same terminal window, start the BOINC Manager:Ĩ. Allow your terminal to pick up the privileges of the new group:ħ. Add your Linux user to the BOINC group to allow the BOINC Manager to communicate with the BOINC clientĦ. Sudo chmod g+r /var/lib/boinc-client/gui_rpc_auth.cfgĥ. Allow group access to client access file: Set the BOINC client to automatically start after you restart your computer:Ĥ. Sudo apt install boinc-client boinc-managerĢ. In a terminal window, run the following command: Some of these steps may not be required at this point in time but the exact installation configuration has changed over time, and these instructions make sure that everything gets set correctly.ġ. Here is WCG's full installation instructions for Ubunut/Debian. World Community Grid's installation instructions for BOINC have documented these in our installation steps for many years (at least since 2014). In order to accomplish #3 you have to add your user account to the boinc group and possible change the permissions on the gui_rpc_auth.cfg file. The arguments have come down to whether we should favor 3 over 2.Īt this time*, the BOINC installation does 1 and 2. Allow a user to launch the BOINC manager under their account and connect to the BOINC core client started in via item 1ĭue to the way apt and yum install software, I am not aware of any approach nor have I seen anyone make a proposal to make all three of the above work.Automatically start the BOINC core client when Linux starts.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |