Posts by Michael MacKay

1) Questions and Answers : Unix/Linux : Force client to upload? (Message 74669)
Posted 27 Jan 2005 by Profile Michael MacKay
Post:
The only solution I have found is the following:

1) kill the BOINC and SETI@home clients

2) edit the file client_state.xml

3) change the min_rpc_time value to 0

4) re-launch BOINC

Primitive, but effective. It is surprising that the BOINC client
does not more easily address this very obvious requirement.
2) Questions and Answers : Unix/Linux : -return_results_immediately (Message 6211)
Posted 10 Jul 2004 by Profile Michael MacKay
Post:
> Step 1. happens immediately after the WU is crunched and may fail because of
> missing internet connection. Then BOINC set a deleay (increasing up to 4
> hours) and retry after this deleay time. On windows dialup hosts BOINC asked
> (if customized) befor connect to the internet, don't know if this works on
> linux. Have no dialup linux.
>
> Step 2. happens normally when the client ask the scheduler for new work.
> Because this can be to long to wait for some users, they use the option
> -return_results_immediately. This means BOINC didn't wait until there
> is need for new work, it connect the scheduler after each upload. In other
> case BOINC is collecting the reports about the uploads.
>
> You can force BOINC to connect the scheduler manually with the option:
> -update prefs [URL] where URL is the projekt URL.
>

This doesn't do anything.

On a Solaris box doing dial-up PPP:

# ./boinc_3.18_sparc-sun-solaris2.7 -update_prefs http://setiathome.berkeley.edu
2004-07-10 14:54:37 [---] Starting BOINC client version 3.18 for sparc-sun-solaris2.7
2004-07-10 14:54:37 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-07-10 14:54:37 [SETI@home] Host ID is 61100
2004-07-10 14:54:37 [---] General prefs: from SETI@home (last modified 2004-07-09 14:03:29)
2004-07-10 14:54:37 [---] General prefs: using separate prefs for home
2004-07-10 14:54:37 [SETI@home] Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
2004-07-10 14:54:46 [SETI@home] Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
2004-07-10 14:54:46 [SETI@home] Project prefs: no separate prefs for home; using your defaults

And at this point the output hangs indefinitely, and there is no network
traffic. So how do I connect to the SETI@home server when I'm actually
connected to the Internet, and not according to some mystery schedule
determined by the BOINC software?

There must be many participants, like me, who will make a dial-up connection
because we have finised work to upload. But BOINC doesn't give us the option:
by the time we notice the work is ready, it is too late. Since we're not
connected, we get:

Can't resolve hostname setiboincdata.ssl.berkeley.edu (host not found)

and then something like:

Backing off 1 hours, 8 minutes, and 35 seconds on transfer of file setiathome_3.08_sparc-sun-solaris2.7

Tough luck for us, I guess, for not being on-line at the correct second!

Disappointed...

Michael






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