• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Basic Seti@home question & seti driver

R

RigorousT

Senior member
I don't have time to do more than a simple search and didn't come up anything to answer the following:

I have multiple computers (4), 3 with constant internet access and one dial-up. What's the easiest way to delegate WUs? Is it alright to just run SETI Driver on each computer and let it cache say 2 WUs, or am I better of using a more complex proxy/caching system?

The reason I ask is because once in a blue moon I have to restart one of my comps and I seem to lose my WU progress. Also, with the dialup computer, what happens to the WUs it completes but doesn't send right away?

Thanks for any answers you can offer.

RT
 
You can set up Setiqueue on one of your constant-connection machines and have the other 2 constant-connection ones upload/download WUs through/from it. You can also run SETI on the Setiqueue machine and it can upload/download through itself (by adding a "-proxy localhost" parameter on that machine's client). Then you can setup SetiDriver on the dialup with a nice amount of WUs and configure it to dialup manually (although it can do it automatically) to upload completed WUs, ie., "asking" before uploading. If you have enough there, it'll just crunch away until the cache runs out.

Normally, if you had a single WU complete and it can't upload right away, the machine will sit idle trying to upload every hour on the hour, forever.

Also, when a machine crashes, you don't normally lose WU progress unless you're running it in a RAM disk. The client is pretty good about saving its state and should start where it left off.
 
If you don't want to hassle with a proxy though, you could just have SETI driver on each of the machince with a good ammount of WUs cached. I myself opted for SETI Q, but you don't have to if you don't want the extra setup.
 
If your machines are on a local LAN you may want to look into SetiQueue.
SetiDriver is a good alternative, but I would set it to about 10 WU's in case of a outage at Berkeley.
The one on dialup is best on SetiDriver and set to manual connect unless you don't mind it dialing in it's self.
The WU's that are complete will just be held till it connects and then all will be sent and fresh ones retrived.
It is best to shut down the Seti program before re-booting(at least on a Win9x machine) as sometimes you will loose any work that has not been writen to disk.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top