Open terminal
Code: Select all
cd /var/lib
sudo chmod -R 777 boinc-client
Code: Select all
cd /var/lib
sudo chmod -R 777 boinc-client
Hi Carl and Mark
Hi MarkWoodles wrote: ↑Thu Sep 03, 2020 8:53 am Carl is correct, 'localhost' is the right way to connect locally.
I have a similar problem on one of my hosts (also a Linux 32 core Xeon coincidentally) but after a power cycle, BM just sits there "disconnected" rather than asking for a project.
Usually selecting "localhost" as the computer to connect to will fill in the password automatically but not in this case, to get it to work I have to select "localhost" then manually type the password in. All fine after that.
Doesn't happen on any other host so I expect there's a file corrupted somewhere or a setting that needs changing. I don't reboot too often and don't really use BM much on that host (I CAN connect remotely) so I haven't bothered finding out why it does it or how to fix it.
Code: Select all
boinccmd --project_attach http://www.rechenkraft.net/yoyo/ account_key
Code: Select all
boinccmd --project http://www.rechenkraft.net/yoyo/ update
Code: Select all
boinccmd --set_network_mode never
Code: Select all
boinccmd --set_network_mode always
Hi CarlChelseaOilman wrote: ↑Thu Sep 03, 2020 2:23 pm I use BAM on all my computers. If you had BAM set up you could change BOINC settings through their website and wouldn't even need BM on the host. The password you need to use with localhost is in the BOINC folder in the gui_rpc_auth.cfg file.