Command-line-only client?

Message boards : BOINC client : Command-line-only client?
Message board moderation

To post messages, you must log in.

AuthorMessage
Peter Humphrey

Send message
Joined: 25 Nov 13
Posts: 30
United Kingdom
Message 84033 - Posted: 26 Dec 2017, 17:08:03 UTC

I have a 4-core, 64-bit Celeron machine running Gentoo with SELinux. It has plenty of spare time but no GUI, and I'd like to run a BOINC client on it. I'd use boincmgr on another machine when necessary.

Is a command-line client still available? And is this idea sensible anyway?
ID: 84033 · Report as offensive
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 272
Australia
Message 84036 - Posted: 27 Dec 2017, 9:43:30 UTC

With Debian/Ubuntu flavours of Linux you would just install the boinc-client package. The manager is usually in the boinc-manager package. I have a bunch of Raspberry Pi’s that are all headless so that’s how I installed them. Just remember to setup gui_rpc_auth.cfg and remote_hosts.cfg so another manager or BOINCtasks can access it. There is also boinctui that runs from the command line.
MarkJ
ID: 84036 · Report as offensive
Peter Humphrey

Send message
Joined: 25 Nov 13
Posts: 30
United Kingdom
Message 84037 - Posted: 27 Dec 2017, 11:29:48 UTC - in response to Message 84036.  

Hello Mark,

I should have thought of this myself, but it took your help to get me on the right track. All I had to do was to set USE="-X" on the "emerge boinc" command and it all went like a charm (that's how Gentoo installs only the command-line version; there isn't a separate package). I've used remote access before, so I knew about gui_rpc_auth.cfg, but I can't find a remote_hosts.cfg anywhere on the system. Still, it seems to be working.

Many thanks for the hint.
ID: 84037 · Report as offensive
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 272
Australia
Message 84038 - Posted: 27 Dec 2017, 11:47:10 UTC
Last modified: 27 Dec 2017, 11:48:38 UTC

In Debian there is a boinc meta package that has both boinc-client and boinc-manager. I expect it installed both but no matter you don't have to use the manager that's on the machine if it installed it.

Again in Debian (I haven't used Gentoo sorry) the remote_hosts.cfg and the gui_rpc_auth.cfg files live in the boinc data folder (\var\lib\boinc-client). The remote_hosts.cfg lists the other computers that are allowed to control your boinc-client. It contains a list of names or IP addresses, each one on a separate line, so you can restrict access.
MarkJ
ID: 84038 · Report as offensive
Peter Humphrey

Send message
Joined: 25 Nov 13
Posts: 30
United Kingdom
Message 84041 - Posted: 27 Dec 2017, 13:48:31 UTC - in response to Message 84038.  

Interesting. It seems that, in Gentoo, remote access either is allowed or is not; I can't see an equivalent of Debian's remote_hosts.cfg, neither in the client nor in the full GUI version. This is a surprise, as Gentoo prides itself on flexibility and customisability. Perhaps I should raise a feature request some time.

Although Gentoo does use meta-packages elsewhere, boinc doesn't have one; if you specify USE=-X to the package manager you get just the CLI client, or if you say USE=X you get the full package. By saying USE=-X I got only six packages: four perl modules, a package to convert docbook to man and info, and the boinc client itself. Nothing else is present. Very economical.

Thanks again Mark. I'm a happy bunny today.
ID: 84041 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5075
United Kingdom
Message 84127 - Posted: 31 Dec 2017, 17:38:01 UTC - in response to Message 84041.  

I can't see an equivalent of Debian's remote_hosts.cfg ...
remote_hosts.cfg is an optional file that you would create yourself, if needed. It is part of the generic BOINC file-set, and not limited to any one distribution or even operating system.

Details are in Controlling BOINC remotely: you also need to ensure that the data traffic (requests and replies) doesn't fall foul of any generic security traps like firewalls.

SekeRob's <allow_remote_gui_rpc> is a perfectly acceptably alternative route, provided you can trust everybody with access to your local LAN.
ID: 84127 · Report as offensive
jada4p

Send message
Joined: 29 Jul 15
Posts: 5
Czech Republic
Message 84202 - Posted: 4 Jan 2018, 16:59:38 UTC

I wanted to run some BOINC project on my mostly idle router Turris Omnia (CPU: Marvell Armada 385, dual-core 1.6 GHz; open source Turris OS, based on OpenWrt - for more see https://doc.turris.cz/doc/_media/omnia/omnia_datasheet_1gb_rgb.pdf).

I installed Ubuntu Xenial in container and BOINC there. SFSG.

Because I encountered repeated errors "Authorization failure: -155" issuing many boinccmd
commands, I removed BOINC installation from the container and reinstalled it. But this error persisted even after purging and reinstalling BOINC!

In last attempt first boinccmd was OK, but next ended again with the same error - even though this command was OK,
boinccmd --lookup_account https://lhcathome.cern.ch/lhcathome/ `mail` `password`

following commands were not:
boinccmd --project_attach https://lhcathome.cern.ch/lhcathome/ `account`
Authorization failure: -155
boinccmd --get_state
Authorization failure: -155


Could anybody please advice?
ID: 84202 · Report as offensive

Message boards : BOINC client : Command-line-only client?

Copyright © 2024 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.