Specifications

154 System Software Diagnostics Guide — September 2006
Runtime Trace Facility (RTF) Reference
28.4 Restrictions and Limitations
Keep the following restrictions and limitations in mind when using RTF:
• If you run full RTF logging on high-density systems, you may experience I/O throughput
degradation. It is recommended that you do not run RTF with full logging on high-density
systems or any field-deployed systems. Instead, use just the default error-enabled logging.
• If you install the Intel Dialogic system release software on a FAT32 formatted hard drive, the
RTF tool will generate an Error after install attempting to launch error message. The error
message appears because FAT32 does not support file system access control. However, RTF
will continue to function.
• The Intel Dialogic system software installation routine creates a usr\dialogic\log directory.
When the system software is installed on a Mandriva* (formerly Mandrakesoft) Linux system,
the Mandriva security utility (msec), which automatically runs every hour, may reset the
access permissions to this ...\log directory. To avoid the resetting of permissions, you must
perform the following before running RTF:
1. Issue the
echo $SECURE_LEVEL command. The Mandriva Linux system will return a
number that indicates the current system security setting.
2. Add the following line to the perm.n file (located in /usr/share/msec/perm.n), where n
indicates the security setting number returned in the previous step:
\var\log\dialogic\* current xxx
Where xxx indicates the desired access permission setting for the directory.
3. After you change the perm.n file, run
msec n
so that the change will take effect immediately.
• When RTF logging is enabled, logs are stored in the $(INTEL_DIALOGIC_DIR)\log directory.
You should take necessary precautions to ensure that the directory never fills.
• Occasionally, errors that appear in the RTF log can be ignored in certain circumstances. Check
the “Release Issues” chapter in the Release Update for the Intel telecom software you are
using (System Release or Host Media Processing [HMP]). Such errors will be listed and
explained in the “Release Issues” table.
28.4.1 Guidelines for Editing the RTF Configuration File
Keep the following rules in mind when editing the RTF configuration file:
1. Do not change the name of the file. The filename must remain at its default setting.
2. The RTF configuration file is broken down into four sections. The sequence of the sections
must always be as follows:
a. RTFconfig
b. Logfile configuration
c. Global configuration
d. Module configuration
3. RTF uses the following default log file names: