Seti: getting ready to load up for a dump, need seti driver help

titanmiller

Platinum Member
Jan 5, 2003
2,123
2
81
I am planning on saving up WUs for a dump on Sunday the 23rd. I currently have all of my machines running seti driver with about 2 days of WUs cached. With my knowledge the only way I know how to download new WUs with completed ones is to rename the folders with completed ones (1DONE, 2DONE, 3DONE ect...). Once I am read to dump all I need to do is set the cache size to what I want in the end and that will work, correct?
 

Assimilator1

Elite Member
Nov 4, 1999
24,165
524
126
Would be much easier if you had your own SETIQ ,you could temporarily disable sending results but still get WUs.
Dunno about SETIDriver ,sorry
 

titanmiller

Platinum Member
Jan 5, 2003
2,123
2
81
Just curious, can you point the queue at a proxy or does it always go directaly to berkeley?

I think I have it figured out though, I'm doing it the manual way by renaming done ones, it will work.
 

Smoke

Distributed Computing Elite Member
Jan 3, 2001
12,650
207
106
Just curious, can you point the queue at a proxy or does it always go directaly to berkeley?

The default is for SetiQueue to go directly to Berkeley. You can go through a third party SetiQueue by entering that Queues IP ADDRESS in the Proxy Server area.

I do think setting up your own SetiQueue and doing as Ass1 told you would be the easiest way to accomplish what you want.

Good luck. :)
 

Crazee

Elite Member
Nov 20, 2001
5,736
0
76
You could just set your cache size on SetiDriver to download enough on each machine for what you expect to produce. Then take it off the auto transmit and let it crunch the cache down. When you are done transmitting them for the dump you can change your cache size back to the original amount.
 

titanmiller

Platinum Member
Jan 5, 2003
2,123
2
81
Originally posted by: Crazee
You could just set your cache size on SetiDriver to download enough on each machine for what you expect to produce. Then take it off the auto transmit and let it crunch the cache down. When you are done transmitting them for the dump you can change your cache size back to the original amount.

I think thats what I'm going to do.