Configuring trace properties
You can set up a trace to record diagnostic information for the SafeLinx Client. Your SafeLinx Server administrator might request a trace file from you to help diagnose a problem.
About this task
The trace configuration tools utility also includes
the following settings:
- Trace levels
- The controls
on the Level tab are:
- None
- Turns all logging off
- Errors
- Messages about unexpected events on which you need to act on
- Warning
- Messages about events on which you might need to act on
- Debug
- Data used for problem analysis
- Log
- General information messages
- All
- All messages and statements are logged
- Subsystems
- The controls
on the Subsystems tab are:
- None
- Turns all logging off
- Main
- Messages logged in the main client code
- IP stack
- Messages logged in libipstack.so
- Timers
- Messages logged by timers subsystem
- Link protocol
- Messages logged by the Link Control Protocol
- Header reduction
- Messages logged in libipreduct.so
- API socket
- Messages logged by the TCP sockets used by the application programming interface
- Common
- Messages logged in libwgcmn.so that do not have a specific category
- Compression
- Messages logged in libwgcompress.co
- Port
- Messages logged by the port subsystem (for example, UDP or TCP)
- Device
- Messages logged in the process of sending and receiving data from the SafeLinx Server
- API
- Messages logged by the application programming interface
- Adapter monitor
- Messages logged when the IP interfaces change states
- User
- Messages logged by a particular user ID
- All
- All subsystems are logged
- File
- The controls on the File tab
are:
- Flush log file
- When the box is selected, messages are flushed to the log file as they are written rather than being buffered. This option slows performance and is generally useful only for debugging. The default value is that the Flush log file box is cleared.
- Maximum file size
- Use the Maximum
File Size field to set
the maximum size of your trace file. Trace messages are stored in
a file named /var/log/wc.log. When the file reaches
its maximum size, it is renamed to wc.bak and
a new wc.log file is created for active trace
data. Only two trace files are kept, the active trace file and the
most recent previous file.
- Default: 1400000 bytes
- Range of values: 0 - 2147483647 inclusive