[wingdo]

I've recently noticed the Seti command line version takes a very long time (literally hours) to get new data after sending results. I've never noticed this before most likely because until recently I kept my dock hidden. I'm using the most recent version of SetiDockling to monitor the goings on of my two command line clients. I tried changing the nice level, but it doesn't seem to matter.

This problem seems odd to me as the screen saver version still gets new data right after sending completed units.

Any ideas?

[The_Equivocator]

Are you using the Team Proxy on one but not the other?

The proxy should be a lot faster than connecting to the SETI servers, but takes a long time to initially set up. Set your CLI client to use the team proxy (seti.macnn.com) and let it do its stuff the first time it connects.

[ 05-24-2002: Message edited by: The_Equivocator ]

[Scotttheking]

SETI is totally backed up right now. Their servers were down most of the day yesterday, and their net is again limited. While connecting to the proxy is a good idea, you have to do it before a backup starts, not during. The proxy is almost empty too, because it can't get new units, and wasn't fully stocked before this outage started, so I can't even transfer some units into new members queues.
Sorry.
I'd recommend connecting to it though, and then just waiting.
As for the screensaver vs CLI, you most likely just got lucky. I see the proxy sometimes getting 3 or 4 in a minute, then none for 12 hrs.

Edit: It looks like you might have a slight chance, the proxy has gotten a few WUs tonight.