Message boards :
Number crunching :
Need to enter computer name and password in BOINC manager
Message board moderation
Author | Message |
---|---|
Eric W Send message Joined: 2 Jan 07 Posts: 5 Credit: 165,965 RAC: 0 |
Hi all, First let me say that I am a noob when it comes to Ubuntu. I successfully have BOINC running on this computer. After I setup BOINC view so my Windows boxes can connect to the Ubuntu boxes using BOINC view everytime I start BOINC manager on the Ubuntu I get this error. "Authorization failed connecting to running client. Make sure you start this program in the same directory as the client." I put the computer name and the password in and all is well. Is there somewhere I can store this so I don't have to do this everytime I start the program? Eric |
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0 |
Hi all, I hope I've understood your question correctly. I've had this same thing to happen to me on Slackware. The solution for me (using KDE) was to add a menu entry for the BOINC manager and specify the working directory. I did this on my desktop also so I can start it without calling up the menu. If this is not an option for you (I don't know what window manager you are running) then you could create a simple shell script such as: #!/bin/bash cd /path/to/your/BOINC/directory/here /path/to/BOINC/manager/boincmgr Name it something like StartMgr or something and make it executable. Then execute this to start the manager. This script can be located anywhere on your system as long as the paths are correct. (A usual place to put something like this is in the /usr/local/bin directory. Hope this helps. Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. |
Toby Send message Joined: 26 Oct 00 Posts: 1005 Credit: 6,366,949 RAC: 0 |
If you install BOINC through apt (or the Synaptic package manager) then it takes care of all that for you. The executables go in /usr/bin/ and the working directory with all the config files and project executables is in /var/lib/boinc-client/. It also creates a "boinc" user on the system that your client will run as. This is good for security. A member of The Knights Who Say NI! For rankings, history graphs and more, check out: My BOINC stats site |
Eric W Send message Joined: 2 Jan 07 Posts: 5 Credit: 165,965 RAC: 0 |
Hi all, I think you are describing what I would need to do if BOINC manager would not start which is not the case. The manager starts but is unable to connect to the local computer. Kind of like when you try to connect to a different computer using boinc manager. It asks your for the computer name and a password. So when I start BOINC manager I have to put in the local computer name and then the password that I specified in the gui_rpc_auth.cfg file. This password really has nothing to do with Ubuntu (at least I think it doesn't) as it is not for any particuliar user. Once I enter the computer name and the password the manager runs fine. I hope this is a bit more clear. |
Lord_Vader Send message Joined: 7 May 05 Posts: 217 Credit: 10,386,105 RAC: 12 |
Hi all, Did you... 1) copy the password from the gui_rpc_auth.cfg file and put that into boincview 2) set up a remote_hosts.cfg file with the IP address of your boincview PC Fear will keep the local systems in line. Fear of this battle station. - Grand Moff Tarkin |
Eric W Send message Joined: 2 Jan 07 Posts: 5 Credit: 165,965 RAC: 0 |
Hi all, Yes and Yes. In fact the computers that have boincview installed can connect to the ubuntu boxes with out problems. It is only when I try to connect to boinc manager on the ubuntu boxes (local) that I have the problem. |
Lord_Vader Send message Joined: 7 May 05 Posts: 217 Credit: 10,386,105 RAC: 12 |
Hi all, What happens when you go to "advanced", "select computer", and type in "localhost"? Fear will keep the local systems in line. Fear of this battle station. - Grand Moff Tarkin |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.