- store final network usage in RESULT; write/parse in state file
- final disk and memory usage weren't being written to state file; do so.
- add --network_usage option to example app, to test this stuff
- If you run the client with --run_test_app,
runs "test_app" in the current directory and interacts with it
(and does nothing else).
It can suspend/resume it with arbitrary timing;
this is controlled in run_test_app() (app_start.cpp).
- example app: add --critical_section option.
This lets you test the runtime system for apps that do
most of their work in a critical section (like GPU apps).
- Add some logging messages (conditioned by DEBUG_BOINC_API)
to the runtime system.
- boinc_finish() waits for the timer thread to write final messages;
make sure it doesn't do anything else
(like suspend the worker thread) during this period
working-set size into a fixed-size buffer.
Use %e instead.
TODO: figure out why WSS was huge.
- web: if "en" is primary language, don't read translation files
svn path=/trunk/boinc/; revision=17831
time of day and process ID.
This should prefix all messages written to stderr
by applications or by the runtime system.
svn path=/trunk/boinc/; revision=17687
David Anderson