The Debug log is intended for programmers to diagnose and see any problems associated with the log files created by ListManager. This feature is only available to server administrators. The debug log view in the GUI reads the same text log files which are created automatically by ListManager, which is in the same directory as your ListManager executable. Multiple log files are created over time, usually log1.txt, log2.txt, log3.txt, etc.
To disable the ListManager startup logging, edit lmcfg.txtand include the following line:
$log_startup_messages="no"
View Log Main Page
Displays the complete log, including the time and date of the item, the error level, the subsystem, and the actual error message. To view a smaller, filtered list, click on Filter current view:
Filter Current View
This allows you to filter the view to customize it for what you are looking for. Filters can be set based on subsystems, and error levels. Once you have set the view, click "view" to see the filtered log file.
Configure Log
This page controls what ListManager is actually saving to the log.txt file, and whether a log file will be kept.
Subsystems
Which ListManager subsystems should be logged. By default, all subsystems are selected. Uncheck the subsystems you do not want to log. Click "All" to log all subsystems.
Log Error Level
What level of logging should be performed. Note that many SQL server problems will only be displayed as warnings, not errors.
Log to Console?
Specifies whether ListManager should log to the console window.
Log to File?
Specifies whether ListManager should log to a file. If enabled, ListManager will start a new log file every time ListManager is started, and when the number of lines in the file exceeds Max Lines In File.
Max Lines In File
The maximum number of lines a single file should have before starting a new file. The default value is 100000 lines. The minimum number of lines is 1000.
Max Log Files
The maximum number of log files ListManager should maintain. The default is blank, for unlimited. The lowest number of files that may be allowed is 10.
Saving the Log
To save the log as a text file that you can open with Wordpad
1. Click Download As File.
2. A message appears warning you that the save operation may take some time. To continue, click Save.
3. Click Save again.
4. The Save As dialog appears. Follow the usual steps for saving a file.