Cleanup of parameters that define disk free space requirements.
Previously these were spread around in different places. Now
these are defined by some config.xml options that are used by
PHP pages and by the scheduler code. See a description in
doc/configuration.php.
svn path=/trunk/boinc/; revision=9081
space prefs agree with web page. Bruce's note: this may require
further fixes for two cases. First, if the project prefs are
not the same as BOINC defaults. Second, if the user doesn't want
BOINC to leave any disk space free and on their web preference page
sets 'leave X bytes free' to zero, then this patch will assume they
mean 100MB. But I'm still applying the patch 'cause Walt says that
this is keeping lots of new users from getting work.
svn path=/trunk/boinc/; revision=8954
name of elapsed_time() to elapsed_wallclock_time().
- Backend logging statements on exit() which echo elapsed run time to logs now
do this with much higher printed precision.
- Backend logging, separate scheduler requests with an almost blank line
svn path=/trunk/boinc/; revision=8027
[1] WU error flag set
[2] WU already has canonical result
[3] (report_deadline - current_time) < 25% of WU delay bound
If any of these conditions is true, set the report deadline to the
current time and set the WU transition time to the current time.
The transitioner will then 'do the right thing'.
svn path=/trunk/boinc/; revision=6871
(1) Put core client version number into wreq BEFORE searching for
an app version. Problem is that reply.wreq.core_client_version was only being set in
send_work(), which was too late for the resend_lost_work() part
of the code. You might want to move all the initialization of reply.wreq
out of send_work(). The core client version is needed to see if the
app is compatible with it when calling get_app_version().
(2) In retransmitting lost work, do NOT set the deadline to new
values. Else the result will never time out! But DO reset
the sent_time, to indicate that result was resent.
transitioner:
In the transitioner, make the next WU transition time be the min
of deadlines of the in progress results, NOT the min of the
sent_time+delay bound. Unless a project wants to do dynamic
adjustment of delay bounds for in progress results this should be OK.
CPDN people: I don't think this does any harm for trickles but
you might want to give it a quick look to be 100% sure.
svn path=/trunk/boinc/; revision=6870
values. Else the result will never time out! (David, would it be OK to
simply modify the send_time but NOT the deadline? This would make it easy
to see in the database that the result is being resent.)
svn path=/trunk/boinc/; revision=6868
scheduler.
Problem is that reply.wreq.core_client_version was only being set in
send_work(), which was too late for the resend_lost_work() part
of the code. You might want to move all the initialization of reply.wreq
out of send_work(). The core client version is needed to see if the
app is compatible with it when calling get_app_version().
svn path=/trunk/boinc/; revision=6867
it to delay until a random time falling within the first hour of the following
day. Previously the host would be told to delay one hour, which could lead to
as many as 24 retries in a one-day period.
svn path=/trunk/boinc/; revision=6132
David Anderson