list has been downloaded regardless of whether or not the item counts are
the same.
clientgui/
NoticeListCtrl.cpp, .h
svn path=/trunk/boinc/; revision=21850
using the standard try/catch handlers.
- WIN: Wrap the coproc detection stuff in C++ exception handlers. If for some
reason the Nvidia or ATI APIs cause an exception don't use the GPUs and
don't crash BOINC.
- WIN: rename boinc_ss to boinc_os_ss and ss_app to boinc_ss.
client/
coproc_detect.cpp
win_build/
*.vcproj
svn path=/trunk/boinc/; revision=21849
cost of repeated string conversions (it doesn't appear to mess with
the messages tab performance too much). Inspired by Charlie.
clientgui/
NoticeListCtrl.cpp, .h
ViewNotices.cpp
svn path=/trunk/boinc/; revision=21847
This feature lets you run the BOINC client as a job on grid systems
that handle only 1-CPU jobs;
it disables various mechanisms that prevent multiple clients per host
(which is normally a bad thing).
Old:
- Run the client with a --allow_multiple_clients flag.
This tells it not to use a mutex that prevents
multiple clients per host.
- Run the project with the <multiple_clients_per_host> config flag.
This suppresses two mechanisms:
- (avoid duplicate host records)
on a scheduler request with no host ID,
looks for a host with same domain name, OS type,
and mem size, and assumes the request is from that host
- (job retry)
If we get a request that doesn't have a host ID
but does have a host CPID,
mark its in-progress results as over
NOTE: I CAN'T REMEMBER WHY WE SUPPRESS THIS;
MARK S, DO YOU REMEMBER?
Problem:
if the grid clients attach to a project that
doesn't use <multiple_clients_per_host>, bad things happen.
E.g., if there are several requests at about the same time,
most of them will fail with
"another RPC already in progress" errors.
If a project does include this flag,
it loses protection from duplicate host records.
New:
- If the client is run with --allow_multiple_clients flag,
it passes a <allow_multiple_clients> element
in scheduler requests.
- The scheduler skips the duplicate-host check on
requests that include this flag.
- There is no more <multiple_clients_per_host> scheduler option.
Note: if a project using the old mechanism upgrades to this change,
it will need to use new clients for its grid deployment.
svn path=/trunk/boinc/; revision=21839
for messages intended as notices.
This will avoid showing lots of obscure stuff as notices
for projects with old server code.
svn path=/trunk/boinc/; revision=21836
manager, right now it stores everything in memory but will be extended
in the future.
- MGR: Clean up notice memory on shutdown
clientgui/
BOINCGUIApp.cpp
BOINCInternetFSHandler.cpp, .h
NoticeListCtrl.cpp, .h
stdwx.h
ViewNotices.cpp
win_build/
boincmgr.vcproj
svn path=/trunk/boinc/; revision=21833
only if the previous request was on a different day
AND the current request asks for work.
Sometimes it wasn't getting cleared when it should have.
svn path=/trunk/boinc/; revision=21824
That produced a messed-up query that assigned garbage values to:
host_app_version.turnaround_var
host_app_version.turnaround_q
host_app_version.max_jobs_per_day
host_app_version.consecutive_valid
To repair these:
- set turnaround_var and turnaround_q to zero
- if max_jobs_per_day is outside of
(0..config.daily_result_quota)
set it to config.daily_result_quota
- if consecutive_valid is outside (0..1000), set it to zero
I added a script, html/ops/repair_21812.php, that does this;
if you ran server code between [21181] and [21812], run this script.
- scheduler/transitioner: add <debug_quota> log flag
- changed the build system to always use -Wall
(if we'd done this before, this bug wouldn't have happened)
- fixed a bunch of other compile warnings
svn path=/trunk/boinc/; revision=21812
Rom Walton