Table of Contents
This section controls the debugging message level for the various wacs modules and applications, making it possible to increase the amount of diagnostic output selectively to aid in debugging code or to provide information for putting in useful bug reports. At it's simplest, this section would read:
This will set the global debug level accordingly (once the
read_conf routine has been executed by the application of course).
For more fine-grained control, the debug level in modules can be
specified with module_wacs
or for an application
with app_wacsimport
.
That is module_
and then it's name in lower case
for modules, and app_
followed by the application
name (again in lower case) for applications; tool_
for command line tools, and util_
for programs
normally run by other things (ie the database populators). Thus if
you were working on code for wacsimport, you
might choose to make this section read:
Example 17.2. Sample Of Specifically Targetted Debug
<debug> <global>0</global> <module_wacs>1</module_wacs> <app_wacsimport>5</app_wacsimport> </debug>
These settings would provide some basic extra debugging for the wacs module (key pathnames, etc) and then pretty extreme output for the wacsimport application.