I am using BOINC and then attaching to it with boinc_cmd. I have one project done...and it says it is ready to report but there hasn't been a server ack. Is there a way I can force it to report to the server?

Also an unrelated qustion. If I shut my computer off will boinc resume the last project I was workin on or will it start a new one?

Reporting Work

There are two parts to returning work. First, when a result is completed, it is immediately uploaded and marked as ready to report. Later, it is reported to the scheduler. This is so it can report batches of WU to the scheduler (which is a separate sever than the upload/download servers), and saves on bandwidth for you and the project.

BOINC reports completed work at the first of:

1) The next work request from a project.
2) 24 hours before the deadline.
3) Immediately if the work is completed later than 24 hours before the deadline.
4) Connect every X days after the work is completed.
5) With the next trickle (CPDN only at this point).
6) When the user clicks update.
7) Connect every X days before the report is due. (new with 5.4).

Seti will continue crunching the result it was busy with when you restart the computer. BOINC doesn't crunch.

---

Reporting Work

There are two parts to returning work. First, when a result is completed, it is immediately uploaded and marked as ready to report. Later, it is reported to the scheduler. This is so it can report batches of WU to the scheduler (which is a separate sever than the upload/download servers), and saves on bandwidth for you and the project.

BOINC reports completed work at the first of:

1) The next work request from a project.
2) 24 hours before the deadline.
3) Immediately if the work is completed later than 24 hours before the deadline.
4) Connect every X days after the work is completed.
5) With the next trickle (CPDN only at this point).
6) When the user clicks update.
7) Connect every X days before the report is due. (new with 5.4).

Seti will continue crunching the result it was busy with when you restart the computer. BOINC doesn't crunch.

Ok you say you can do it when the user clicks update. I'm using the command line version I can't seem to find a command to force the update.

Ok you say you can do it when the user clicks update. I'm using the command line version I can't seem to find a command to force the update.

So don't. BOINC will handle it all. Fully automatically.

---

/path/to/boinc_cmd --project project_url update
and when in doubt:
/path/to/boinc_cmd --help
:-)
Hudl

---

It doesn't get any easier... you just get faster.