Been a SETI@HOME user for years - am moving away from Window$.
I have spent a few days trying o get back online using Linux, but so far, no go! :(
I have Ubuntu and have tried their Debian and the file from downloaded from SETI@HOME. No changes in response at GUI part of BOINC.

I have used this install routine:
http://forum.boincuk.com/viewtopic.php?p=17041&sid=a81835f88af94aa177de34682384353b

"sudo chmod +x boinc_5.4.9_i686-pc-linux-gnu.sh (changes the archive to an executable)
sudo ./boinc_5.4.9_i686-pc-linux-gnu.sh (extracts the executable)
sudo rm boinc_5.4.9_i686-pc-linux-gnu.sh (deletes the archive file)
cd BOINC (switches to the directory created by the archive)
sudo ./boinc -attach_project http://setiathome.berkeley.edu xxxxxxxxxxxxxxxxxxxx
where xxxxxxxxxxxxxxxxxxxx is your setiathome account key."

With this I can get the command line portion program to run and download and work.
But upon opening the boinc manager GUI I get no connections:

"...TOOLS/ATTACH TO PROJECT - gives the above response :"BOINC Manager is not currently connected to a BOINC client.Please use the 'File\\Select Computer...' menu option to connect up to a BOINC client.To connect up to your local computer please use 'localhost' as the host name."

Therefore I then go to ADVANCED/SELECT COMPUTER where I get "HOST NAME" and "PASSWORD".

I have tried setiathome.berkeley.eduwith and without the http://, aswell as "localhost" and my password from the message boards, my email address and my account key and and even NOTHING in either or both fields and I STILL get :
BOINC Manager is not able to connect to a BOINC client. Would you like to try to connect again?"

It looks like it is attempting to connect sometimes and yes, I have confirmed that the SETI servers are up and running."

I am using "localhost" as most Google posts say, but can not get the password or even change it because there is no way (even with the CHMOD command) I can NOT read, edit, or even move the gui_rpc_auth.cfg file - I can rename it, but even then it's still locked.
Deleting that file makes no difference.

It's late , I have been at this for hours, and I need to get some rest; here's where I have given up for tonite:
http://www.google.com/search?hl=en&lr=&q=gui_rpc_auth.cfg%2C+ubuntu%2C+permission&btnG=Search
Nothing.

Can anyone help me get connected again?
Pretty please.
Thank you.

MRK

From security reasons it is not recommened to install and let boinc run as root. Please set the onwer (chown) it to a normal user and start it as normal user.
I recommend you to add a seperate user for your boinc client.

The tasks in the installation guide are OK if there will be used without "sudo".
But you can do following :
- add a new user
- sudo "mv YOUR_CURRENT_BOINC_DIR /home/boinc/". /home/boinc is only a example for a the boinc users home directory...
- sudo "chown -R boinc /home/boinc". (User boinc and /home/boinc are examples, too).
- su - boinc
- edit gui_rpc_auth.cfg and change/enter your password
- Start the boinc client : "./boinc_client -allow_remote_gui_rpc"
- Connect from the boinc manager with to the boinc client (localhost or the hostname of your system would be right) and type in the password you have entered in the gui_rpc_auth.cfg.

---

- edit gui_rpc_auth.cfg and change/enter your password

But I AM NOTABLE TO EDIT THIS FILE! It has a red "X" icon ans saysI do not have permissions to modify it!

Curious as to why there's a security risk with running BOINC?

- edit gui_rpc_auth.cfg and change/enter your password

But I AM NOTABLE TO EDIT THIS FILE! It has a red "X" icon ans saysI do not have permissions to modify it!

This is a problem related, to your installation as root. Please reinstall it under a normal user account, as I described it.

Curious as to why there's a security risk with running BOINC?

No, there is no security problem by boinc itself.
But, If there would be a security problem for a example a buffer oferflow, it gain access to your complete system and could overtake the whole system.
If you running as user, it will be restricted by the unix access mechanisms.

---

Curious as to why there's a security risk with running BOINC?

Basic practice on real operating systems: you run nothing as root unless there's a sound reason to do so (and there rarely is, unless you're briefly tweaking some aspect of the system itself).

---

To err is human; to moo, bovine.

Curious as to why there's a security risk with running BOINC?

Basic practice on real operating systems: you run nothing as root unless there's a sound reason to do so (and there rarely is, unless you're briefly tweaking some aspect of the system itself).

I understand, and this may be "SETI Off topic", but then, why do the installers PUT the files in the root??? Surely all Linux users are not programmers or "uber-Geeks" and even so, wouldn't it be a nice reminder or conveniance to say "Create new user or whatever before installing this"?

Will not be able to get back to the Ubuntu til tomorrow, but I appreciate the input. Anyone who wants to chime back in to elaborate on this, as this is the first time I have heard of this issue in a few weeks of Linux-learning.
I don't want to sound like a whiner, but I have also not found any site that takes a noob like me and fundamantally transisions an expereanced DOS/Window$ user into Linux from the perspective of just "making the switch"; as in adding files to the root, permissions, repositories and other nuances that are so different in theory and practice.

Thanks!

I understand, and this may be "SETI Off topic", but then, why do the installers PUT the files in the root??? Surely all Linux users are not programmers or "uber-Geeks" and even so, wouldn't it be a nice reminder or conveniance to say "Create new user or whatever before installing this"?

The installations from applications and let them run with the root account depends on the installations. [/quote]
In general, as Byrn has written, it is a UNIX best (recommended) and most common practice to let applications run as root if they must and install everything else as seperate user.

Will not be able to get back to the Ubuntu til tomorrow, but I appreciate the input. Anyone who wants to chime back in to elaborate on this, as this is the first time I have heard of this issue in a few weeks of Linux-learning.
I don't want to sound like a whiner, but I have also not found any site that takes a noob like me and fundamantally transisions an expereanced DOS/Window$ user into Linux from the perspective of just "making the switch"; as in adding files to the root, permissions, repositories and other nuances that are so different in theory and practice.

A Windows to Unix transition guide was often asked here in the boards. But I have not found a good guide. But I will look around, if I find a good documentation.

---

I understand, and this may be "SETI Off topic", but then, why do the installers PUT the files in the root???

They don't - the BOINC installer defaults to putting the files in the home directory of the user performing the installation.
Therefore, if you're root when you're installing BOINC - its files end up in /root.

You can either logon as "you" and then install BOINC (which as Dotsch has already said, this would resolve your permissions problems too), or you can create a dedicated "boinc user" account and install it under that.

wouldn't it be a nice reminder or conveniance to say "Create new user or whatever before installing this"?

The dangers of doing everything as root are generally well documented in the documentation provided with a Linux distribution. It's simply a part of adapting to a different OS's security model and not something which requires documenting with an application.

(1) first time I have heard of this issue in a few weeks of Linux-learning.
...
(2) I have also not found any site that takes a noob like me and fundamantally transisions an expereanced DOS/Window$ user into Linux from the perspective of just "making the switch"
...
(3) permissions, repositories and other nuances that are so different in theory and practice.

(1) It will likely take more than a few weeks to get yourself settled in but it's well worth the effort.
May I suggest at first that you don't rely on using a GUI? They're very pretty and all that but ultimately, your hands become tied by what the GUI allows you to do instead of what the OS can do for you. When you better understand the underlying system you can then get the best from the GUI. (and unlike that other OS, a Linux GUI is not the OS)

(2) There is no way in which you can just "make a switch", because there are fundamental differences between Linux and Windows (thank $DEITY) which, unless learned, will trip you up time and time again.

(3) Linux != Windows

(end of off-topic drift ;)

---

To err is human; to moo, bovine.

Thanks and I sincerely do appreciate this. However now I find I no longer have a gps_rpc_auth.gfg file, and I can not get BOINC to connect.

Please see this post and PLEASE do reply:

http://setiathome.berkeley.edu/forum_thread.php?id=34470#435875

Thank you, sincerely.

MRK

Thanks and I sincerely do appreciate this. However now I find I no longer have a gps_rpc_auth.gfg file, and I can not get BOINC to connect.

Have you repaired the rights, as I have described you ?
Please stop the BOINC Client. Now, you can easly create the file, with the editor of your choice and enter the password in this file in plain text.
Now start the boinc client againt with the option "-allow_remote_gui_rpc" and you should be able to connect with the boinc manager.

---