[Debug]IOServerLogDirect
- Last UpdatedJun 17, 2026
- 1 minute read
Determines if logging for I/O server traces go directly to the syslog.dat file or are handled via a Kernel task.
Note: If the parameter [Debug]LogDirect is set to 1, the setting for [Debug]IOServerLogDirect will be overridden. Setting [Debug]IOServerLogDirect to zero (0) will only work if [Debug]LogDirect is also set to its default (0).
By default, logging is sent directly to the syslog.dat file ([Debug]IOServerLogDirect=1). This is recommended under the following circumstances.
-
If you have heavy logging enabled for numerous I/O server systems (including driver traces).
-
If accurate timestamping is required. Kernel logging does not accurately reflect the occurrence of events as the Kernel has a fixed processing rate.
-
If exceptions are occurring, direct logging helps to ensure the last traces are in the syslog.dat file. The Kernel logging system has a limit on the buffers that can be used for logging. See [Kernel]ErrorBuffers.
Note: when this parameter is set to 1, no I/O server traces (or driver traces) will appear in Kernel Main window.
Setting this parameter to 0 (along with [Debug]LogDirect=0) may be useful if you have very low logging levels and want to monitor the system from the Kernel Main window. Logging via the Kernel is also useful for older style HDDs that can overload the I/O system.
Allowable Values:
-
0 - Log via the Kernel logging system.
[Debug]LogDirect also needs to be set to 0.
-
1 - Log directly to the syslog.dat file.
Default Value:
1