Log Files
The Qedit server can only communicate with Qedit clients. To help system managers see what is happening with the Qedit process, Qedit for Windows writes to three log files: the access log, the error log, and the trace log.
Console Messages
If Qedit cannot access any of its log files, it writes the log message to the system console. You can also enable console logging with the Debug command in the Option menu of the Qedit client. If someone is having trouble establishing a Qedit for Windows connection and the Qedit log files on the host do not include a message for this connection, check the system console. If Qedit was unable to open the log files, it probably reported the message on the system console.
Access Log
Every time a Qedit client makes a connection to the server process, an entry is written to the access log file in which the IP address of the client is logged. The numeric for the IP address is logged, along with the port number used to communicate with the client.
Error Log
Any error conditions encountered by the Qedit server process are written to the error log file. If you suspect a problem between the client and the server, start your diagnosis by looking at the end of this log file.
Trace Log
By default, Qedit does not log messages to the trace log file. However, you can enable trace file logging by using the Debug command in the Option menu of the Qedit client. The trace log file can grow to become very large because Qedit messages are constantly being added to it. These messages assist in understanding the communication between the Qedit server process and the Qedit client. In many cases, their detailed information is the only way to diagnose a problem.
Log File Names
If you run Qedit as Qedit.Pub.Robelle, the three log files are located in the Qlog group of the Robelle account. If you renamed Qedit or run it from a different group or account, the group and account names for these log files will automatically be adjusted. See the chapter “Installing Qedit” for more details.