Logging Options
Click on Logging under Pragma Fortress Manager dialog to configure what kind of logging, if any, will be done.
Record Logon/Logoff events to Application Event Log:
Configure whether Pragma TelnetServer should create entries in the Windows Application Log whenever users log on or off. These entries can be viewed using the Windows Event Viewer. Event explanations are available in the Event Details, viewed by highlighting the event, and selecting View->Detail&ldots; from the menu.
Keep log file using plain text format:
Check this box to save log files in ASCII text format.
Keep log file using HTML format:
Check this box to save log files in HTML format, viewable through a web browser.
Log File Directory:
Specify the directory for saving log files. In this directory, a subdirectory will be created for each day a telnet connection is made. Within that directory the log files will be saved with the naming convention: username.MMDDHHMMSS.PID.html or username.MMDDHHMMSS.PID.txt.
Use User Credentials for log files:
Check this box to have log files created by the user logged into the server. By default log files are created by the LocalSystem account so that users do not have to be granted read and write permissions to the log file directory. If the log file directory is located on another machine, requiring network authentication, the LocalSystem account cannot be used, so this box must be checked. This box can also be checked if user context is preferred and permissions are granted to the log file directory.
Troubleshooting Log Files
Log Session Output Data:
Check this box to have all output sent from the server written to a file. The file will be created in the configured directory with the filename sshoutPID.txt, where PID is the process id of the current server process, Server PID in the Session Manager. This data will not be formatted in anyway.
Log Session Input Data:
Check this box to have all output sent from the server written to a file. The file will be created in the configured directory with the filename sshinPID.txt, where PID is the process id of the current server process, Server PID in the Session Manager. This data will not be formatted in anyway.
Directory:
Specify the location for the troubleshooting log files.
See also: