Prints messages about allocation of slots, creating/removing files in slot dirs. Results of the round-robin simulation used by CPU scheduler and work-fetch.ĭetails of scheduler RPCs also shows deferral intervals and other low info.ĭebugging information about the screen saver. Network status (whether need physical connection).ĭebugging information about HTTP proxy operations. Show completion status of file transfers.ĭebugging information about GUI RPC operations.ĭebugging information about HTTP operations.ĭebugging information about network communication. Show details of coprocessor (GPU) scheduling.ĬPU scheduler actions (preemption and resumption). Shared-memory messages sent to applications.Īsynchronous copy and checksum of large (> 10 MB) files.ĭebugging information about CPU benchmarks. Shared-memory messages received from applications. The following messages are disabled by default (typically they generate lots of output, and are used for debugging): The start and completion of file transfers. The start and completion of compute jobs (should get two messages per job). The following messages are enabled by default: The flags within are used to selectively turn different types of messages on and off (0 for off, 1 for on). (Note: some changes in the section take effect only when you restart the BOINC client). If you edit the file while BOINC is running, the changes will take effect only if you select the Advanced / Read config file menu item. To create or edit the file, use a text editor such as Notepad, and save it in your BOINC Data directory or project directory. If the file is absent, the default configuration is used. The configuration is read from: cc_config.xml, nvc_config.xml, and (for each project) app_config.xml. When using the example, delete the square brackets. Note: square brackets in examples indicate optional parts. Some parameters can be controlled using different mechanisms pick the one that's best for you. There are three configuration mechanisms: These messages appear in the Event Log of the BOINC Manager they are also written to the file stdoutdae.txt (Windows) or to standard output (Unix). The BOINC client can be configured to control its behavior and to produce more detailed log messages.
0 kommentar(er)
