Most BOINC projects have one and the same server name for all of the various project server functions (master, downloads, uploads, scheduler, web interface, message boards). But Rosetta@home has got...
Scheduler server: srv4.bakerlab.org
(upload server and web server: boinc.bakerlab.org)
...a separate host name of the scheduler. For bunkering, it is sufficient to block
only the scheduler (srv4.bakerlab.org). That way, uploading of result files keeps working, and you can still access the web site and forums (boinc.bakerlab.org).
After the start of the contest, precisely...
After the
stats table at the contest site was initialized, which should be shortly after May 5, 00:00 UTC, enable networking again to let the boinc client upload and report the results, as well as fetch more work.
...after SETI.Germany's tables were initialized, remove the block to the Rosetta scheduler again, then trigger a project update in the boinc client to report the results.
In the /etc/hosts-method, the block is implemented as an entry like
127.0.0.1 srv4.bakerlab.org
in the file /etc/hosts on Linux, or C:\Windows\System32\drivers\etc\hosts on Windows. Caveat: Some systems are using a caching resolver. Typically, such a resolver monitors the host file for changes and picks your edit up immediately. But some don't, and need to be triggered to reload (or reboot the computer). If unsure, after you edited the hosts file, use boincmgr's advanced view, click [Update] on Rosetta@home, and check the event log. The method succeeded if the message "Scheduler request failed: Couldn't connect to server" appears. (To be safe, you can perform this test
before you start bunkering, or while you have network transfers suspended in the boinc client.)
If you prefer to block uploads too, add the line
127.0.0.1 boinc.bakerlab.org
in the hosts file. Of course then you will lose access to the Rosetta web site and message boards as a side effect.
To remove the block again later, just remove the above line(s) from the hosts file, or put a # comment sign in front of this line. Again, most resolvers will pick up this reversal immediately, but some may require a reload trigger (or simpler: host reboot).
Note,
if you want to retain the ability to modify target CPU time on the go (see
post #21) even while you are bunkering, then either use the "suspend networking method" (this blocks uploads but still enables user-requested scheduler requests), or use the /etc/hosts-method
with a block of boinc.bakerlab.org and temporarily switch to the "suspend networking method" when you need to access the Rosetta@home web site.