Alonzo wrote:

i have a problem caching workunits...

i am only crunching seti.
my workstation is a 2 x 2,2 GHz Xeon with an optimized client.

Do you mean an optimized BOINC client, or an optimized SETI app?

1 workunit takes about 1:25 to 1:30 to finish.

my preferences are:
Connect to network about every : 4 days

but caching is only about half a day.
if i raise to 10 days, then caching is about 1 day.
if i finish a wu the client is requesting only a few seconds new work
(to 20-30sec)
if seti is offline for more than 1 day i am running out of wu.
sometimes boinc is saying that my pc is overcommited, but i am only
crunching seti and nothing else.

Have a look at your host page to see if your most recent benchmarks
look reasonable for the system. If they're lower than those of
similar machines, it might help to get BOINC to run benchmarks again,
making sure the computer isn't doing anything else that would slow it
down during the test. Also check your preferences to make sure BOINC
knows it can use both your processors--the daily quotas are per CPU.

If low benchmarking isn't the problem, and assuming you actually have
an optimized SETI app but a standard BOINC client, you might want to
look at an optimized or "calibrating" client like TruXoft's:

<http://boinc.truxoft.com/core-cal.htm>

It can take a while to settle in, but from what I've heard it
eventually does a much better job of estimating the amount of work a
system running an optimized app can do, and makes credit claims more
in line with those from standard setups.

There are several other optimized clients out there; the reason I
recommend TruXoft's (again, just from reading, not from personal
experience) is most relevant to multiple projects, that it can be
disabled from tinkering with the workload and credit claims for
non-optimized apps. But if you're only running S@h you can choose any
of several modified BOINC clients without fear of 'cheating' on other
projects or distorting resource shares.

Of course the 'recommended' solution to out-of-SETI-work problems is
to attach to a second project, assigning it a small resource share if
you like. ;p

i am running several pc and none of them have problems to cache 4
days.

is the only solution to uninstall the client and reinstall and
reconnect to seti??

I don't see what good that would do, unless you have reason to
suspect a corrupt installation.

-- 
Odysseus