Community
Participate
Working Groups
Currently, the Terminal Telnet connector is capable of logging its input byte stream for debugging purposes: * Create directory C:\eclipselogs (on Windows) or /tmp/eclipselogs (on UNIX) * File "tmterminal.log" will be created with byte stream logging I think that all Terminal connectors should be capable of logging the byte streams, so this should be moved to the common Terminal widget. Use "Logger.encode() referenced-by" to see how the Telnet connector currently does it. Also, the method for switching on logging should be improved to allow arbitraray target directories for the log files, since local policies could forbid users to write into the hard-coded directories. I'd be in favor of using the Platform Debug (.options) method for this.
Created attachment 82842 [details] A patch that adds a decorator stream coming from the baackend LoggingOutputStream is a FilterOutoutStream that does the logging
Created attachment 82843 [details] mylyn/context/zip
checked in
Verified with TM 2.0.3 candidate on Linux-GTK RHEL4: When directory /tmp/eclipselogs exists, each "SSH", "Telnet", "Serial" terminal connectors log to file tmterminal.log in that directory.