From 986b8f87be4296cea2910d961eb3a4d93dc312d7 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 7 Nov 2015 09:51:24 +0000 Subject: [PATCH] Document the new session-logging command line options. If I'm going to announce them as a feature in 0.66, it would be embarrassing to forget to mention them in the documentation. --- doc/using.but | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/doc/using.but b/doc/using.but index a2d8c271..5448b81a 100644 --- a/doc/using.but +++ b/doc/using.but @@ -953,3 +953,20 @@ DSR/DTR. For example, \cq{-sercfg 19200,8,n,1,N} denotes a baud rate of 19200, 8 data bits, no parity, 1 stop bit and no flow control. + +\S2{using-cmdline-sshlog} \i\c{-sessionlog}, \i\c{-sshlog}, +\i\c{-sshrawlog}: specify session logging + +These options cause the PuTTY network tools to write out a \i{log +file}. Each of them expects a file name as an argument, e.g. +\cq{-sshlog putty.log} causes an SSH packet log to be written to a +file called \cq{putty.log}. The three different options select +different logging modes, all available from the GUI too: + +\b \c{-sessionlog} selects \q{All session output} logging mode. + +\b \c{-sshlog} selects \q{SSH packets} logging mode. + +\b \c{-sshrawlog} selects \q{SSH packets and raw data} logging mode. + +For more information on logging configuration, see \k{config-logging}.