I can't connect to anything on Linux or Mac. I'm running Debian on a PC and Mac and the lastest version of OS X on another Mac. I can't connect on any of these machines. Many of my Mac and Linux using friends are experiencing the same problems. It worked once on my Debian machine and then never again. It now claims I have the wrong password but its the correct one.

I suspected that more time and effort was spent on the windows version and tried it out on "Poor Bastard" (named so because that poor machine is running the worst "OS" ever made) I was able to connect with the same password the Linux and Mac versions claimed was invalid. The windows very did, however, constantly crash often taking out the entire computer but that happens with other apps as well so it has nothing to do with the seti software.

On Dec 15th we have decided to end our participation with setiathome if a better software isn't posted. I hate the idea of giving up on the project but I clearly have no choice, the software doesn't work. I started this on 21 Feb 2001, not as long as others but long enough to be sad about losing it.

I know many will tell me they got it running ok, but all I hear from people I know IRF is that they can't get it running.
I ask that the software hackers for the Unix/Linux/Mac version try to produce something as stable as the old unix versions.
If anyone can help resolve this we would greatly appreciate it.

---

After a great deal of convincing. I got everyone to use the command line only with kboincspy as the UI info display and something similar with the Macs but with no GUI info just a term.
This is fine for me but everyone else wants the cool looking G U I s along with the CL Lapps. Like setiathome and ksetispy. ksetispy was also capable of starting and stopping setiathome. I suspect the author of ksetispy/kboincspy is already on the case there. So that's not an issue. So for my Gnu Linux KDE users, I think this will be resolved soon via kboincspy (I hope) so only one app will have to be launched as before. I don't know about my Mac friends. I need to look into the problem further.

Anyway, HELP! Come on setiathome hackers, Unix/Linux/Mac users are your friends too. Why are we always getting the short end of the stick when it comes to software?

The Collective

---

After a great deal of convincing. I got everyone to use the command line only with kboincspy as the UI info display and something similar with the Macs but with no GUI info just a term.
This is fine for me but everyone else wants the cool looking G U I s along with the CL Lapps. Like setiathome and ksetispy. ksetispy was also capable of starting and stopping setiathome. I suspect the author of ksetispy/kboincspy is already on the case there. So that's not an issue. So for my Gnu Linux KDE users, I think this will be resolved soon via kboincspy (I hope) so only one app will have to be launched as before. I don't know about my Mac friends. I need to look into the problem further.

Anyway, HELP! Come on setiathome hackers, Unix/Linux/Mac users are your friends too. Why are we always getting the short end of the stick when it comes to software?

The Collective

KBOINCSpy (and maybe your Mac prog) works fine for controlling Seti/Boinc if you remove the password in gui_rpc_auth.cfg and replace it with a single carriage return (ie press enter) on the first line. To quote Scarecrow in this post, "To eliminate the password, a single carriage return on the first line of the file is needed."


The password is there for additional security only for remote access. If you don't access that Boinc installation remotely, you don't really need it.

Edit: removed reverse polish notation grammar.

---

Need help? Check out the excellent Unofficial BOINC-Wiki!
'We are the BOINC. Prepare to be assimilated.'

"KBOINCSpy (and maybe your Mac prog) works fine for controlling Seti/Boinc if you remove the password in gui_rpc_auth.cfg and replace it with a single carriage return (ie press enter) on the first line. To quote Scarecrow in this post, "To eliminate the password, a single carriage return on the first line of the file is needed."
The password is there for additional security only for remote access. If you don't access that Boinc installation remotely, you don't really need it."

As far as I've been able to tell kboincspy doesn't start the client. We don't use the gui anymore because, even with the above mods to the gui_rpc_auth.cfg, it continues to fail. Running the command line version with kboincspy as a gui progress display works well. It would be nice if it could control the client like ksetispy did.

We have also discovered out kseti-screensaver doesn't work anymore.

---

I assume that you're starting the BOINC Manager from an icon or menu entry. Be sure to set the working directory for the program to your BOINC installation directory. This effectively 'cd's into the dir and enables the manager to find the authentication file and start up correctly.

---