Specifications

System Software Diagnostics Guide — September 2006 155
Runtime Trace Facility (RTF) Reference
• rtflog-<year><month><day>-<hour>h<minute>m.<second>s.txt when preservation
mode is OFF.
• rtflog-<year><month><day>-<hour>h<minute>m.<second>s_p.txt when preservation
mode is turned ON.
4. The Global configuration section can only appear one time in the RTF configuration file.
5. If a there is configuration information which conflicts in the global and module sections (for
example, the global section enables a trace label for a client, but the module section disables
this same label for the same client), then the module configuration overrides the global
configuration.
6. Configuration information which is repeated later in the file will take precedence. For
example, if there are two module configurations for spwrvoice, the configuration information
lower in the file will dictate tracing behavior for that module.
Note: This should not be done, but it is mentioned here so the behavior can be recognized if
this situation occurs by error.
7. RTF is case sensitive. Therefore, the trace labels “Error” and “error” are considered to be two
distinctly different trace labels.
8. Simultaneous tracing of multiple Intel Dialogic libraries may have an adverse effect on system
performance.
9. If you run full RTF logging on high-density systems, you may experience I/O throughput
degradation (specifically if you enable tracing on the MClient name MUTEX). It is
recommended that you do not run RTF with full logging on high-density systems or any field-
deployed systems. Contact customer support before enabling extensive logging. Instead, use
just the default error-enabled logging.
10. RTF affects running processes/applications only. If you enable RTF prior to starting your
application, the RTF will not provide trace information until your application has started.
11. If you wish to dynamically edit the RTF trace levels while your application runs, it is not
necessary to stop RTF. Instead, perform the following:
a. Open the RTF configuration file.
b. Customize the settings in the RTF configuration file.
c. Save and close the RTF configuration file.
d. Issue the
rtftool reload command to reload RTF configuration file and restart the
RTF engine.
Note: Keep in mind that changes made to the RTF configuration file will not be reflected in
the RTF output until the tool has been reloaded.
12. At any time, you can issue the
rtftool command to pause/restart RTF. RTF will not provide
trace output while it is paused. Refer to Section 28.5, “rtftool Command”, on page 156 for
more information.
13. Save the original RtfConfigWin.xml file or RtfConfigLinux.xml file, as it is advisable to return
to the original logging level when finished using the RTF logging mechanism.