FileLogger.dll

A module that logs all messages to file if no logging module is loaded no error messages will be logged thus it is hard to find problems.

Configuration Sections

This is a wrapper page the actual data is on the following page FileLogger/config

Overview

This section has options for how logging is performed with the [FileLogger] module. First off notice that for logging to make sense you need to enable the “FileLogger.dll” module that logs all log data to a text file in the same directory as the NSClient++ binary if you don’t enable any logging module nothing will be logged.

The options you have available here are

Option	Default	Description
debug	0	A Boolean value that toggles if debug information should be logged or not. This can be either 1 or 0.
file	nsclient.log	The file to write log data to. If no directory is used this is relative to the NSClient++ binary.
date_mask	%Y-%m-%d %H:%M:%S	The date format used when logging to a file
root_folder	exe	Root folder if not absolute

debug

A Boolean value that toggles if debug information should be logged or not. This can be either 1 or 0.

Default

0

Values

Value	Meaning
0	Don't log debug messages
1	Log debug messages

file

The file to write log data to. If no directory is used this is relative to the NSClient++ binary.

Default

nsclient.log

date_mask

The date format used when logging to a file

Default

%Y-%m-%d %H:%M:%S

root_folder

Root folder if not absolute

Default

exe

Values

local-app-data

The file system directory that contains application data for all users. A typical path is C:\Documents and Settings\All Users\Application Data. This folder is used for application data that is not user specific. For example, an application can store a spell-check dictionary, a database of clip art, or a log file in the CSIDL_COMMON_APPDATA folder. This information will not roam and is available to anyone using the computer.

exe

Location of NSClient++ binary