// DBOINCP-300: added node comment count condition in order to get Preview working ?>
Mato Atom
Joined: 5 Sep 06
Posts: 1
Credit: 14524
RAC: 0
5 Sep 2006 16:13:43 UTC
Topic 191792
(moderation:
)
why do you have to send reports manually? isn't there an option to let it do it automaticly when it finished a job? i dont see a reason why you need to do it manually every time...
If you just let it be, it will report it automatically.
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).
As Jorden stated, it will do it automatically when it needs to.
BOINC is mean to set and forget. I have it running on 7 different machines, all of which I only check every few days just to make sure nothing looks funny. My jobs are all done, reported, and they run fine. I see an occassional errored result, but usually because of circumstances beyond my control (usually project related issues, like bad headers, badly create result, etc.).
Allow the software to do it's own thing. You will be less stressed, and so will the servers, since you are not clicking update every time.
Send Report Automaticly?
)
If you just let it be, it will report it automatically.
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).
As Jorden stated, it will do
)
As Jorden stated, it will do it automatically when it needs to.
BOINC is mean to set and forget. I have it running on 7 different machines, all of which I only check every few days just to make sure nothing looks funny. My jobs are all done, reported, and they run fine. I see an occassional errored result, but usually because of circumstances beyond my control (usually project related issues, like bad headers, badly create result, etc.).
Allow the software to do it's own thing. You will be less stressed, and so will the servers, since you are not clicking update every time.