Linux cmd line client too buggy


Advanced search

Questions and Answers : Unix/Linux : Linux cmd line client too buggy
Message board moderation

To post messages, you must log in.

AuthorMessage
nermy

Send message
Joined: 5 Mar 00
Posts: 2
Credit: 67,963
RAC: 0
United States
Message 200244 - Posted: 1 Dec 2005, 17:16:22 UTC

It's too bad that setiathome is forcing all to move to boinc before the bugs get worked out.
I can't get it to work on most of the computers I work with. different problems with different versions of boinc. Too many dependency issues and just plain buggyness.
I'm going to have to stick with the classic setiathome client until they stop accepting my jobs or fix boinc.

I can contribute cpu cycles, but not time debugging.
stevie
ID: 200244 · Report as offensive
Dotsch
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 2422
Credit: 919,393
RAC: 0
Germany
Message 200275 - Posted: 1 Dec 2005, 18:12:17 UTC
Last modified: 1 Dec 2005, 18:14:02 UTC


It's too bad that setiathome is forcing all to move to boinc before the bugs get worked out.

Which bugs do you mean ? - On my systems it runs very well.


I can't get it to work on most of the computers I work with. different problems with different versions of boinc. Too many dependency issues and just plain buggyness.
I'm going to have to stick with the classic setiathome client until they stop accepting my jobs or fix boinc.

I can contribute cpu cycles, but not time debugging.

Which problems do you have ?
ID: 200275 · Report as offensive

Questions and Answers : Unix/Linux : Linux cmd line client too buggy


 
©2025 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.