| Subject: Re: cmdline problems |
| From: James J |
| Date: 20/07/2004, 22:05 |
"Brian Dickens" <newsgroups@(remove-this-part)briandickens.demon.nl>
expounded in news:OvQKc.562$Ue.125@text.usenetserver.com:
James J wrote:
Had you bothered to read this group, you would have seen that SETI
is down at the moment. Nobody is able to send or retrieve WU's.
Actually, that's only half true (unless things have changed in the
last several hours). I've been able to get new WU's. I just haven't
been able to send in any results.
Nope -- even when I cleared out my finished WU so SETI@Home could
retrieve one, it still didn't work. The new BOINC SETI@Home just
quietly sits here also, it cannot retrieve new data.
=- Brian Dickens, the Netherlands
Maybe you just caught it at a bad time. During the "problem time" I was
able to get more WUs (for "classic" S@H) more than once, but not return any
results.
IAC, everything seems to be back to normal today. Was finally able to
send in my 20-something results, and get a couple more WUs.
BTW, it sounds like you're not using a queue/cache program. You might
want to consider one. I'm using SetiQueue and having 20+ results waiting
to be sent back didn't prevent it from retrieving more WU's. No need to
try to clear out finished WU's to get new ones or anything like that.
James