I'm not all that fluent in Linux, so bare with me. I have read about 5 different pages on how to install BOINC on Linux (Ubuntu), and I still can't figure how to configure my client for my account.

This is what I've got so far:

# ./boinccmd --get_project_status
======== Projects ========
1) -----------
   name:
   master URL: http://setiathome.berkeley.edu/home.php/
   user_name:
   team_name:
   resource share: 100.000000
   user_total_credit: 0.000000
   user_expavg_credit: 0.000000
   host_total_credit: 0.000000
   host_expavg_credit: 0.000000
   nrpc_failures: 2
   master_fetch_failures: 3
   master fetch pending: yes
   scheduler RPC pending: yes
   trickle upload pending: no
   attached via Account Manager: no
   ended: no
   suspended via GUI: no
   don't request more work: no
   disk usage: 0.000000
   last RPC: 0.000000
   project files downloaded: 0.000000

So far, I have found exactly ZERO pages explaining how to setup my account in a straightforward way. Sure, I've seen this:

   boinccmd --join_acct_mgr URL name password

But I have no idea what that means, because all of these commands do nothing:

   boinccmd --join_acct_mgr http://setiathome.berkeley.edu/home.php DrStrangepork <account_key>
   boinccmd --join_acct_mgr http://setiathome.berkeley.edu/home.php DrStrangepork <weak_account_key>
   boinccmd --join_acct_mgr http://setiathome.berkeley.edu/home.php [email protected] <my_setiathome_account_passwd>

I have also tried to connect to this Linux machine from a Windows machine running the BOINC Manager, but I have no idea what the password is for this client. Again, I have tried my account key, my weak account key and my account password, and they all result in the Manager doing nothing. The IP of this client is 10.10.70.1, and there is no proxy required.

Thanks in advance,
Rick

I did a quick install the other day.

I just opened a terminal window and typed:

sudo apt-get install boinc-client boinc-manager

It installed OK (but it was version 5.10.45, old version of Ubuntu), I opened BOINC Manager, connected to a project with my email address and password for that project and I was up and running.

I don't think I've ever used the command line to set up BOINC on any of my Linux boxes. Perhaps you are trying to do something more complicated than me. I am not a Linux expert BTW!

Al.

Well, I forgot to mention that I cannot use any X-Windows/Gnome/etc on these boxes. They are strictly shell-based. Using the BOINC Manager would probably have been quite easy, but I can't use it.

boinccmd --project_attach http://setiathome.berkeley.edu <account key>

boinccmd --project_attach http://setiathome.berkeley.edu <account key>

That resulted in a new project under './boinccmd --get_project_status' that looks exactly like the first project just without the 'home/' at the end, and neither project does anything.

I have also tried to connect to this Linux machine from a Windows machine running the BOINC Manager, but I have no idea what the password is for this client.

The password is in the file gui_rpc_auth.cfg (on your linux box).

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

Do you have more than one Linux machine? There is a linux server attached to your account that has 6 tasks assigned to it:

http://setiathome.berkeley.edu/show_host_detail.php?hostid=6400842

The password is in the file gui_rpc_auth.cfg (on your linux box).

I checked that out, but that password doesn't work either.

Do you have more than one Linux machine? There is a linux server attached to your account that has 6 tasks assigned to it:

http://setiathome.berkeley.edu/show_host_detail.php?hostid=6400842

Looks like the client is running now, but I still can't attach to it. Even from the command line, every boinccmd command I run results in this:

Authorization failure: -155

I'll try rebooting and see if anything improves.

Using the apt-get package instead of the BOINC package worked fine. Still can't connect using BOINC Manager from another host, but boinc_cmd is working fine, and all hosts are talking back to SETI and working on tasks.

Still can't connect using BOINC Manager from another host, but boinc_cmd is working fine, and all hosts are talking back to SETI and working on tasks.

you need a remote_hosts.cfg file with the ip address or host name to allow a remote host to connect:

Controlling BOINC remotely

Claggy