Changes between Version 2 and Version 3 of ReportBugs


Ignore:
Timestamp:
Jul 27, 2007, 4:35:50 PM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReportBugs

    v2 v3  
    3333
    3434== Incorrect behavior ==
    35 If BOINC behaves incorrectly, we usually need the core client's message log to figure out what's going on. The message log describes what the core client is doing. It's identical to what's shown in the Messages tab of the Manager. By default the core client writes only a few messages. More detailed messages are enabled by turning on '''logging flags'''. This is done by editing the file cc_config.xml in your BOINC directory. For example, the following turns on the task_debug and cpu_sched flags (1 turns a flag on; 0 or unspecified turns it off):
     35If BOINC behaves incorrectly, we usually need the core client's message log to figure out what's going on. The message log describes what the core client is doing. It's identical to what's shown in the Messages tab of the Manager. By default the core client writes only a few messages. More detailed messages are enabled by turning on [ClientMessages '''logging flags''']. This is done by editing the file cc_config.xml in your BOINC directory. For example, the following turns on the task_debug and cpu_sched flags (1 turns a flag on; 0 or unspecified turns it off):
    3636{{{
    3737<cc_config>