How do I turn on logging?

The programs that make up VA have various logging options that can be enabled to produce log files that may be of use to the developers in the event of any problems.

All of these options should normally be turned off. Only enable them if asked to by the developers to help investigate a problem. Be aware that some of the options will produce large log files, which will use a lot of disk space.

General Logging

This causes VA32.exe to write debug information to the file debug.txt in the root directory of the drive containing the VA messagebase.

It can be turned on and off by setting and clearing the "General Logging" checkbox on the "System" tab of the Tools | Options dialog.

While logging, the log file grows contiuously. If the file exceeds a preset limit (currently around 5MB) VA will ask you whether you want to delete the file.

Note With default Windows permissions, if you run VA from a non-Administrator account VA will not be able to create the log file. You should create the log file from an administrator account and set the access rights on it so that it can be written by all users.

Comms Logging

This causes Inet32.exe to write debug information to a text file while connecting to the internet. It can be turned on and off for each internet service individually by setting the "Logging Options" level in the "Logging" tab of the "Comms Setup" dialog for that service. You must also specify a filename for the file to which the log information will be written.

This log file does not grow continuously, but is recreated as an empty file every time inet32 runs. Make sure you save the file after a blink or it will be overwritten.

Import Logging

This causes Import32.exe to write debug information to a log file as it imports messages to the VA message base. The log file is always called import.log and will be found in the top level VA messagebase directory.

There is no GUI mechanism to turn import logging on and off, but you can set it by editing the "Import Debug Level" setting in the [Main] section of ashmount.ini. "Import Debug Level" should be set to a number from 0 to 3, where 0 means no logging, and 3 means maximum logging.

While logging, the log file grows contiuously. If the file exceeds a preset limit (currently around 1MB) VA will ask you whether you want to delete the file.

Message Rule Logging

VA's internet comms module can record the messages received that match message rules and display a list in actions/information. This option is enabled for all users for a given service by placing a line saying "Kill logging=YES" in the section for that service in ashmount.ini.

VA can also log the application of message rules during import. This option can be enabled for all users, for all services, by adding the line "Rule Logging=YES" to the [Main] section of ashmount.ini. The logged information is appended to the file intdlg32.log in the top level VA messagebase directory, this file can grow quite quickly and should be deleted from time to time.

VA can also produce some debug information about message rules as they are read from the rule file. This can be enabled by setting "Rule Debug File" to some valid writable filename and "Rule Debug Level" to a number (at least 2 seems to be needed to produce any output) in the [Main] section of ashmount.ini. This is generally less useful than the "Kill logging" setting mentioned above.

 
vaosfaq/turnonlogging.txt · Last modified: 02.12.2017 16:15 by daniel
 
Recent changes RSS feed Driven by DokuWiki