On Sun, 20 Mar 2005 20:53:29 +0100, Louis Holleman
<louis@holleman.demon.nl> wrote:

With all respect, I don't think that's the case. I've been watching
Seti over the past few days and when I set it to "connect every 2
days" it doesn't do just that. It goes fetching WU's for what it
thinks it needs for 2 days and starts crunching. After some time it
decides it will run out of WU's within 2 days and gets some more to
keep it going again for 2 days, etc. Meanwhile it also sends in
results etc. So the statement on the preferences page is a bit false,
it won't just connect every 2 days but it will indeed cache FOR to
days and keeps that cache going whenever it can.
Someone telling me different: go ahead, but it's not what I've seen
over the past period running Boinc/Seti :-)

Mmmm.... I thought I've seen that....   looking at stdout.txt (the log
file) here's some more details:
I've set prefs to "connect only every 2 days"  (so that's what you'd
think it would do).
Here's what it does:
2005-03-13 19:00:30 [---] May run out of work in 2.00 days; requesting
more
and it gets new WU's. Now you wud think: it will connect again in 2
days eh?  NO, not really:
2005-03-14 08:52:59 [---] May run out of work in 2.00 days; requesting
more
and it fetches a bunch more WU's.
It happens again: not after 2 days, but:
2005-03-14 23:57:40 [---] May run out of work in 2.00 days; requesting
more
and again it gets new WU's.
2005-03-15 14:52:10 [---] May run out of work in 2.00 days; requesting
more
2005-03-16 05:27:04 [SETI@home] Started upload of
27dc04ab.20913.15872.322166.29_1_0
(because it was sending in results too)
2005-03-16 09:30:19 [SETI@home] Started upload of
27dc04ab.20913.15872.322166.50_1_0
(same thing; actually this was the last unit I got in before the whole
thing cracked up)

I hope you're convinced now :-)

Louis