Core client: debugging

Command-line options

Some command-line options intended for debugging:

-exit_when_idle
Exit when we're not working on anything and a scheduling server gives a "no work" return.
-no_time_test
Don't run performance benchmarks; used fixed numbers instead.
-exit_after N
Exit after about N seconds
-giveup_after N
Give up on file transfers after N seconds (default is 2 weeks)
-limit_transfer_rate N
Limit total network traffic to N bytes/sec.
-min
Put client in the background after starting up

Logging and error output

The core client writes error messages to stderr. This mechanism is reserved for serious problems, i.e. those that reflect bugs in the core client program or conditions that require user intervention.

In addition, the core client can write a variety of "logging" information to stdout. The logging options are read from a file log_flags.xml. This file has the following format: 

<log_flags>
    [ flags ]
</log_flags>
The flags are as follows:
<task/>
Log the start, restart and completion of computational tasks.
<file_xfer/>
Log the start, restart and completion of file transfers.
<sched_ops/>
Log connections with scheduling servers.
<state_debug/>
Log changes to the "client state" data structures.
<task_debug/>
Log debugging information about task execution.
<file_xfer_debug/>
Log debugging information about file transfers.
<sched_op_debug/>
Log the request and reply messages of exchanges with scheduling servers.
<time_debug/>
Log the passage of time.
<http_debug/>
Log debugging information about HTTP operations.
<net_xfer_debug/>
Log debugging information about network communication.
<measurement_debug/>
Log debugging information host speed, platform, disk space, etc measurements.