Message boards : BOINC Manager : boinccmd debian, can't connect.
Message board moderation
Author | Message |
---|---|
Send message Joined: 23 Apr 10 Posts: 2 |
Hi. First off, i am new to Linux, so don't hate me. :) I have tried searching google for information, but i can't find any good answer on how to get it to work. when i try to attach my client to a new project i get this message. tian@********:~/seti/BOINC$ boinccmd --project_attach can't connect to local host I know i need the project URl and so on, just used it as an example. So, my question is how do i get it to work? Where do i go from this? // Tian |
Send message Joined: 20 Dec 07 Posts: 1069 |
Is the BOINC client (./boinc) running already? Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) |
Send message Joined: 23 Apr 10 Posts: 2 |
Hahaha, oh man do i feel stupid. :P Thanks alot for the fast answer. :) Works like a charm now. Cheers /Tian |
Send message Joined: 19 Jan 07 Posts: 1179 |
Just in case someone blindly follows your advice in a situation where it doesn't apply... Your suggestion works in this case because he installed from the BOINC-provided self-extracting archive. However, if you install from Debian packages, you should never run the BOINC client typing 'boinc'. It's already running as soon as you install the package, and will start again when the system boots. Many people run the client manually, usually to try attaching a project (not knowing that's done with 'boinccmd', not 'boinc'), usually with $HOME as their current directory, scattering BOINC's state all over it. It's made worse by the fact that boinccmd works only if your current directory is BOINC's data directory (/var/lib/boinc-client if you install from Debian packages), or if you give the GUI RPC password explicitly. |
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.