Something seems a little odd with my BOINC manager in that the SETI@home project is not showing any "Communication deferred" count down in the Projects tab.

If I do a manual update it starts a 5 minutes count down, does this approximatley three times then disappears. The event log goes quiet with nothing happening at all.

Once it is in this state how will it contact the server again to recheck if work is now available? Normally I see the "Communication deferred" increase in duration not simply disappear.

This is normal if there is no work to report - if you wait long enough BOINC will go through the cycle automatically.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I believe there are one or more hidden timers at work as well. If you go to the Projects tab in BOINC Manager, select S@h, then click on the Properties button, one of the properties you should see displayed, down near the bottom, is "NVIDIA GPU task request deferred for:". (That's assuming you have an NVIDIA GPU, of course.) I suspect there might be a similar timer for CPU requests, but that doesn't seem to be displayed there.

EDIT: Actually, now I see that the CPU timer is displayed on my daily driver, which is completely out of work, whereas it wasn't on the machine I was looking at a moment ago, which still has some work left.

I believe there are one or more hidden timers at work as well. If you go to the Projects tab in BOINC Manager, select S@h, then click on the Properties button, one of the properties you should see displayed, down near the bottom, is "NVIDIA GPU task request deferred for:". (That's assuming you have an NVIDIA GPU, of course.) I suspect there might be a similar timer for CPU requests, but that doesn't seem to be displayed there.

EDIT: Actually, now I see that the CPU timer is displayed on my daily driver, which is completely out of work, whereas it wasn't on the machine I was looking at a moment ago, which still has some work left.

I also see them both only when out of work. What is odd they both say deferred for 10 minutes but the main Communication deferred message counts dowm from 5 minutes.

Very confusing how this works. Seems to retry approx once a hour.

I also see them both only when out of work. What is odd they both say deferred for 10 minutes but the main Communication deferred message counts dowm from 5 minutes.

Very confusing how this works. Seems to retry approx once a hour.

Click on the Properties tab to see how long the CPU/GPU backoffs are.

---

Grant
Darwin NT