[Debug]LogDirect
- Last UpdatedJun 19, 2026
- 1 minute read
Determines if logging to syslog.dat for some subsystems is directly sent to the log file or handled via a Kernel task. This mainly involves logging for internal system errors and the I/O server system.
Note: A new INI parameter [Debug]IOServerLogDirect has been added to control I/O server traces. If [Debug]LogDirect=1, then a non-default setting for [Debug]IOServerLogDirect will be overridden.
By default, logging is sent via the Kernel (LogDirect=0). This is recommended for users who want to look for exceptions in the Kernel Main window. Logging via the Kernel is also useful for older style HDDs that can overload the I/O system.
Using LogDirect=1 (log directly to syslog.dat) is recommended under the following circumstances.
-
If you have logging enabled for numerous trend or I/O server systems.
-
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: Not all messages to the Kernel Main window use the function which [Debug]LogDirect controls. Even when using LogDirect=1, some miscellaneous messages may appear in the Kernel.
Allowable Values:
-
0 - (log via the Kernel logging system)
-
1 - (log directly to the syslog file)
Default Value:
0