In article <eg5r31128gs30samoap2ppg6r327h21d30@4ax.com>, f/fgeorge
<ffgeorge@yourplace.com> writes

That'll fix the problem!!!! NOT LIKELY!!! You set your cache at the
max of 10 days, workunits expire in 14 days. You will only connect to
Berkeley every 10 days, Berkeley goes down and you are stuck with a
ton of unreportable and then expired workunits! Tell me again how
raising your cache is better!!

You may well be correct, and this outrage (Cogent internet connection
problem) may take a few days to sort. 

Perhaps, with luck, today - as it is now about 08.30 am in California.
Certainly if it is sorted soon, and the hammering by all with WUs ready
and wanting to u/l, we may just slide through and keep busy.

Not knowing how big your SETI/Boinc cache is, I have SETI Classic set
for 4 days. This normally gives capacity for outrages, and returns WUs
in a decent time. Looks like a SETI/Boinc cache of about 5-6 days is
idea for longer outrages, and still meet the 14 day "out of life" WU
limitation.

Just think Einstein, it has plenty of work and will keep your computer
busy during the outages. Just set your priorities for something like
90% Seti and 10% Einstein. You will crunch for Seti and then only 10%
ofthe time you will also be crunching for Einstein. Why Einstein,
because it is the only project with workunits right now. All the rest
of the DC projects are sufferring because Seti is down too!
All the DC projects are listed here:
http://distributedcomputing.info/projects.html
You must sign up for each one individually.

-- 
John Clark