|
|
|||||
This page is a part of XSecurePro64 online Help Manual. |
|||||
| 6. Configuring XSecurePro64 | < previous | content | next > |

Options that you can specify within this tab are for debug purposes. They exert influence on all X applications of the package (XServer, X Clients, etc ...).
A value (one from None, Minimal, Advanced, Full) in this field
denotes a tracing level for collecting keyboard trace information for your X-session
(e.g., Events of pressing/releasing of keys) to the log file.
None disables keyboard tracing.
If checked, this check box enables writing out any special debugging information into
the c:\xservert.dat trace file.
Be careful when using this option because of significant decreasing the XServer's performance
and a large size of the trace file.
If this check box is checked, then all font requests from X clients (with resolve messages) will be stored in the xserver.out file. This option is useful for analysis of the font accessibility and resolving font problems by XServer.
When the Network trace check box is selected, it enables network tracing between XServer and remote X clients.
A value in this field that you can choose from the list box denotes a tracing level for collecting network trace information for your X-session to the log file.
In this entry field, you can specify a name for a log file to store network trace data.
In this entry field, you can type in a length for the allocated memory (in number of lines)
to flush it to the trace file.
The value of 0 means a "very large" buffer (as much as your system allows).
Caution: when a system crash happens, the data in the allocated memory is lost.
| 6. Configuring XSecurePro64 | < previous | content | next > |
| Copyright © 1999 - 2009 LabtamTM Inc. | |