The Logging tab is used to configure a variety of logging mechanisms.
Be careful when running batch files and redirecting stdout and stderr. If you use batch file commands, such as “timeout” and “pause” that expect stdin, then your batch file may crash. This behaviour was observed on earlier versions of Windows, including Server 2008 and 7. Windows 10 and Server 2016 appear immune to this problem. Try using “waitfor” instead.
For more information about log rolling, see Log Rolling and Counter Placeholders.
The following table describes the fields provided on the Logging tab.
| Fields | Description |
| Event Logging | Select the checkbox to enable logging to the Event Log. |
| Debug Log Level | Select the logging level. The following options are available:
Debug Logging is somewhat verbose and should be enabled only when attempting to resolve FireDaemon Pro service configuration issues.Execution tracing will be included in the debug log file once the relevant FireDaemon Pro service(s) have been restarted. This environment variable has no effect if Debug Logging is disabled. |
| Append Logs | Select the checkbox to append all log entries to the Debug, Stdout, and Stderr log files. If this option is disabled, the Debug, Stdout, and Stderr log files are overwritten each time the service starts. If the service crashes and is restarted, the Stdout and Stderr log files will be overwritten in this case. Note: If FireDaemon Pro cannot write to any of the specified log files, it will write an error event to the Windows Application Event Log. |
| Debug Log File | The full path and name of the destination file for the debug log messages. Environment variables can be used in the name. This field is enabled only when the Verbose or Very Verbose option is selected in the Debug Log Level field. |
| Output Capture | |
| Capture Stdout in File | Enter the full path and name of the destination file for the Stdout output (Standard Output, which is the console text output stream from the program being run as a service).Stdout/Stderr capture is unbuffered and cached.The Stdout/Stderr stream is captured only when the program's output buffer is flushed. Therefore, the successful capture of output is dependent upon the program's behaviour. Stdout/Stderr messages may be truncated if the program exits suddenly of its own accord. FireDaemon Pro flushes Stdout/Stderr upon program restart and termination. |
| Capture Stderr in Stdout | Select this checkbox to enable capturing Stderr (Standard Error – the console text output stream specifically marked as errors from the program being run as a service) to the same log file that is used for the Stdout stream. |
| Or Capture in File | This enables Stderr to be captured in a separate file from Stdout. Enter the full path and name of the destination file for the Stderr output that is separate from the Stdout file. |