still so beta


log in

Advanced search

Questions and Answers : Wish list : still so beta

Author Message
dory2
Send message
Joined: 10 May 04
Posts: 1
Credit: 783
RAC: 0
Germany
Message 7287 - Posted: 13 Jul 2004, 5:17:28 UTC

Have set up one machine (Linux) with boincseti around July 1st, after I heard, that it's not beta anymore.

Did not get any WUs for the first 10 days or so. How can Berkeley ask us to switch from Classic to boinc, if it does not work ?

Therefore I wish:
First fix the problems and then give it to the masses.

Since there are WUs available, my machine is returning appx. 2 results per day. I know, that it takes a while, before credits are granted, but there doesn't even seem to be a method of tracking, how many results where returned. A text search on the local file system for "pending", "claimed" and other similar terms, did not point to anything usefull, so the only way seems to be the account info on the web site. In the account info, "this feature is turned off".

Again: How can Berkeley ask us to switch from Classic to boinc, if it does not work ?

Therefore I wish:
First fix the problems and then give it to the masses.

And I wish:
Give us the chance to monitor ou system properly, without the need of any fuctionality from Berkeley. A reasonable logfile or something would be very helpful.

Starting boinc with ./boinc & puts the process in background as expected, but closing the console then also closes the ./boinc client and seti. What is it good for to exit on SIGHUP ? Classic did not do that.
Pushed boinc to the background using "at -mf ./startboinc now" where startboinc is a shell script, that just starts the boinc client.

I wish: Make boinc behave like a normal program. SIGHUP should not exit.


Baseline: Too early to switch to boinc

Questions and Answers : Wish list : still so beta

Copyright © 2014 University of California