BOINC - SETI????

[compudog]

SETI BOINC, I want to run it on some of my dedicated crunchers. I want some simple, easy instructions for installing and running the CLI version (if there is such a thing) and yes, I am lazy. (Actually not lazy but have little free time for muich of anything lately.)

I no longer have access to the email account I used when I originally set up SETI (OMG!! I used the SS version!!) that's before I found the TeAm and became addicted to stats etc... MTR's, beating DSL reports etc.

As a SETI mentor, I am embarassed to say I don't know much about setting up BOINC. I can set up the CLI client with Seti Driver, Seti Spy etc in my sleep.

As always, thanks.

 

[Rattledagger]

Since you haven't got access to the old email-address, go here
http://setiweb.ssl.berkeley.edu/create_account_form.php

After typing in name & email, hit "Create Account" & check your email. By following the pages you will set up your preferences and be transported to the download-page.

Remember to goto
http://setiweb.ssl.berkeley.edu/team_display.php?teamid=30191
and hit "Join this team"


As for the actual client, on windows after installing it will automatically run the gui as part of the install-process. If you don't need proxy-settings, just paste
http://setiathome.berkeley.edu/
as project-URL & your account-key.

Any proxy-settings must be entered before attacking, and currently there's a bug if needs username/password on http-proxy.

Then you see this works, exit the gui. In your BOINC-directory you have boinc_cli.exe and this is the cli.
Either place a short-cut to this in your start-up-folder (make sure you don't have a shortcut to the gui), or install it as service (on NT 4 or later) with boinc_cli.exe -install

Note, currently there's a bug so if you logs off your computer the service will unfortunately stop.
Also, atleast in XP, you must maybe go into the service-controll-panel & change the user it's running as to "localsystem". Must also manually start the service 1st time, or re-boot.

boinc_cli /? for more command-line-switches.


After they've got stable servers, they'll fix the small bugs. Also, the setup-process will probably be slightly changed later on then they hits M2. (separate gui & terminating "classic").

 

[compudog]

Thanks Rattledagger. I'll give it a whirl.

 

[compudog]

Grrr. keep getting errors.


--- - 2004-07-07 09:35:23 - Starting BOINC client version 3.19 for windows_intelx86
--- - 2004-07-07 09:35:23 - Project / found in state file but not prefs.
--- - 2004-07-07 09:35:23 - No general preferences found - using BOINC defaults
http://setiathome.berkeley.edu/ - 2004-07-07 09:35:51 - Project prefs: using your defaults
--- - 2004-07-07 09:35:51 - Fewer active results than CPUs; requesting more work
--- - 2004-07-07 09:35:58 - Fewer active results than CPUs; requesting more work
http://setiathome.berkeley.edu/ - 2004-07-07 09:35:58 - Requesting 16288 seconds of work
http://setiathome.berkeley.edu/ - 2004-07-07 09:35:58 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
http://setiathome.berkeley.edu/ - 2004-07-07 09:36:05 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-07 09:36:05 - Message from server: No work available
SETI@home - 2004-07-07 09:36:14 - Resetting project
SETI@home - 2004-07-07 09:36:14 - Detaching from project


I will keep trying but will continue to run SETI1.

 

[Rattledagger]

Another little bug, since there currently isn't any available work can't successfully attach to the project either.

 

[Freewolf]

Originally posted by: Rattledagger
Another little bug, since there currently isn't any available work can't successfully attach to the project either.

i would say no work is a bit more then a little bug .

 

[Rattledagger]

"no work available" is not a bug, but that you can't attack to a project then there isn't any work is a bug.

Built-in-caching & multi-project-support should lead to you still can keep crunching, even one of the projects can be down for scheduled maintanance, lost connection, crashes or other things. The current is probably down to "server optimizations".

 

[JHutch]

One of the improvements of the BOINC system is that we won't have the same work unit crunched 15 times by different people. The system keeps very close tabs on who gets what work unit. Once a unit has been crunched by three different computers and the results all agree, that work unit is "done." The old SETI system kept sending it out if they needed more work units. Right now, BOINC has more people ready to crunched than they have work units ready to send out, so we are getting fairly regular "out of work" messages. It'll get better as they work out the bugs and get more splitters online.

JHutch