Logging categories

The logging categories, non-Launcher usage, provide a variety of debugging information. They are used to determine which severity levels and components to debug.

LogX=n

Provide the specific category, such as Trace, Debug, Info, Warning or Fatal, for X and 0 to turn that logging category off, or 1 (to turn that category on) for n.

Example: LogTrace=1
Logging Category Value Description
LogTrace 0 Disabled
  1 Enables the logging of sequence of events

Example Results:

Before Resource Pending <map>

After Resource Pending <map>

LogDebug 0 Disabled
  1 Enables the logging of information to diagnose adapter connection behavior

Example Results:

New audit file name <name>

Adapter wildcard.<wildcard>

LogInfo 0 Disabled
  1 Enables the logging of general information about the state of adapter connections

Example Results:

:Map started

InitPendingHigh reached

LogWarning 0 Disabled
  1 Enables the logging of issues that are not severe, but might be important to know

Example Results:

Resource Manager table too small - using default

Map warning <map>

LogError 0 Disabled
  1 Enables the logging of critical adapter connection errors

Example Results:

Map failure <map>

Socket failure <socket_type>

LogFatal 0 Disabled
  1 Enables the logging of a fatal error

Example Results:

Corrupted MMC file during initialization <mmc_name>

Adapter listener Initialization failure <adapter>