I have Dual CPU's and while the client understands this....

>> Fewer active results than CPUs; requesting more work

...the server thinks I'm hogging resources:

>> Message from server: Not sending work - last RPC too recent: 4 sec

...but it never sends the unit. I took hours, long after this unit finished to get another and it would only give me one. Always complaining that I am asking too quickly....

>> Deferring communication with project for 10 minutes and 0 seconds

Is this a bug, or have I done something wrong?

I changed my preferences from 1-2 days work to 2-5, and am now recieving plenty of work!!!

Berkeley had problems to produce enough WU's at the moment. May be they have underestimated the using of the cache. In the classic SETI@home most users only download one WU and then crunch, now everybody download many WU's before crunching the first.

The Not sending work - last RPC too recent: 4 sec is nothing to worry about. There is a protection on server side, so that a client can connect only every 10 minutes. With this message Deferring communication with project for 10 minutes and 0 seconds the client reports that the server told it to wait this 10 minutes.

After some tries this should be fix itself by automatic. But if there is no work on the scheduler the message will comne back. The client then starts to increase the delay up to round about 4 hours step by step and then it will try again.

Greetings from Bremen/Germany

Jens Seidler