Cisco Headend System Release 2.7 Installation Guide
Enable Tracing on the Application Server
4017650 Rev C
183
Syntax For The trace.cfg File
You must enter the trace.cfg entries using the following syntax:
tracename programcontext tracelevel
The following table explains each component of the trace.cfg entry. Use the
components to build entries for the trace.cfg file.
components to build entries for the trace.cfg file.
Part
Description
tracename
Identifies the subset of code within an executable file that you want to
trace. The tracename component can be the trace name that was
registered in the executable code, or it can be the library file name
without the lib and .* extensions.
trace. The tracename component can be the trace name that was
registered in the executable code, or it can be the library file name
without the lib and .* extensions.
The tracename component is optional. You can include tracename to
turn on tracing for a given subset of code, such as a library. If it is
omitted, tracing is turned on in all contexts for the tracename.
turn on tracing for a given subset of code, such as a library. If it is
omitted, tracing is turned on in all contexts for the tracename.
programcontext
Identifies the process that you want to trace. The programcontext
component can be the name of the executable file or the trace name
that was registered in the executable code.
component can be the name of the executable file or the trace name
that was registered in the executable code.
tracelevel
Identifies the level of detail that you want to capture for this process.
Examples:
_ipgui 2—The programcontext is _ipgui, and the tracelevel is 2. This entry starts
a level 2 trace on the _ipgui process.
a level 2 trace on the _ipgui process.
gui _ipgui 1—The tracename is gui, the programcontext is _ipgui, and the
tracelevel is 1. This entry starts a level 1 trace on code labeled gui in the _ipgui
process. (This code may be in the gui library.)
tracelevel is 1. This entry starts a level 1 trace on code labeled gui in the _ipgui
process. (This code may be in the gui library.)
All _ipgui 1—The tracename is all, the programcontext is _ipgui, and the
tracelevel is 1. This entry starts a level 1 trace on all code in the _ipgui process.
tracelevel is 1. This entry starts a level 1 trace on all code in the _ipgui process.
Enabling the Tracing Function on the Application Server
In order to enable or disable tracing for an Application Server process, you must edit
the /dvs/appserv/tmp/trace.cfg file. Each line in this file represents a trace
command for an Application Server process.
the /dvs/appserv/tmp/trace.cfg file. Each line in this file represents a trace
command for an Application Server process.
Lines that begin with a pound sign (#) are comments. The tracing function ignores
these lines. Therefore, in order to disable tracing, you can simply add a pound sign
to the beginning of the corresponding line.
these lines. Therefore, in order to disable tracing, you can simply add a pound sign
to the beginning of the corresponding line.
Also, some of these comment lines may contain trace commands that have been
disabled. To enable tracing, you can simply remove the pound sign from the
beginning of those lines.
disabled. To enable tracing, you can simply remove the pound sign from the
beginning of those lines.
Complete these steps to enable the tracing function for an Application Server
process.
process.