na toll - ein Rechner konnte WUs ziehen und jetzt bringen die anderen:
--
2004-07-14 20:53:23 [---] Finished CPU benchmarks
2004-07-14 20:53:24 [---] Resuming computation and network activity
2004-07-14 20:53:24 [---] Fewer active results than CPUs; requesting more work
2004-07-14 20:53:25 [---] Fewer active results than CPUs; requesting more work
2004-07-14 20:53:25 [http://setiathome.berkeley.edu/] Requesting 34560 seconds of work
2004-07-14 20:53:25 [http://setiathome.berkeley.edu/] Sending request to scheduler:
http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi2004-07-14 20:53:26 [http://setiathome.berkeley.edu/] Scheduler RPC to
http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
2004-07-14 20:53:26 [http://setiathome.berkeley.edu/] General preferences have been updated
2004-07-14 20:53:26 [SETI@home] Message from server: No work available
2004-07-14 20:53:26 [SETI@home] Message from server: No work available
2004-07-14 20:53:26 [---] General prefs: from SETI@home (last modified 2004-07-14 11:34:13)
2004-07-14 20:53:26 [---] General prefs: no separate prefs for home; using your defaults
2004-07-14 20:53:26 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-07-14 20:53:26 [SETI@home] Deferring communication with project for 1 hours, 0 minutes, and 0 seconds
2004-07-14 20:53:26 [SETI@home] Deferring communication with project for 1 hours, 0 minutes, and 0 seconds
--
ist hoffentlich ein Serverseitiger Fehler... :-/