+This section describes the command line options that Plink accepts.
+
+\S2{plink-usage-options-v}\c{-v} show verbose messages
+
+By default, Plink only displays any password prompts and the output of
+the remote command. The \c{-v} option makes it print extra
+information about the connection being made, for example:
+
+\c Server version: SSH-1.5-OpenSSH-1.2.3
+\c We claim version: SSH-1.5-PuTTY
+\c Using SSH protocol version 1
+\c Received public keys
+\c Host key fingerprint is:
+\c 1023 e3:65:44:44:bd:b1:04:59:bc:e2:3d:a1:4d:09:ce:99
+\c Encrypted session key
+\c Using 3DES encryption
+\c Trying to enable encryption...
+\c Successfully started encryption
+\c Sent username "fred".
+\c Sent username "fred"
+\c fred@example.com's password:
+
+This information can be useful for diagnosing problems.
+
+\S2{plink-usage-options-ssh} Protocol selection options
+
+Plink is most useful when using the SSH protocol. However, it allows
+you to interface to all the protocols supported by PuTTY. You can
+specify the option \c{-ssh} on the command line to select the SSH
+protocol; you can also specify \c{-telnet}, \c{-rlogin} or \c{-raw}
+to select other protocols.
+
+\S2{plink-usage-options-P}\c{-P port} connect to specified port
+
+If your server machine is running its SSH service on a port other
+than the standard one, you can specify an alternative port number to
+connect to using the \c{-P} option, like this:
+
+\c plink -ssh login.example.com -P 5022
+
+\S2{plink-usage-options-pw}\c{-pw passw} login with specified password
+
+A simple way to automate a remote login is to supply your password
+on the Plink command line. This is \e{not recommended} for reasons
+of security. If you possibly can, we recommend you set up public-key
+authentication instead. See \k{pubkey} for details.
+
+Note that the \c{-pw} option only works when you are using the SSH
+protocol. Due to fundamental limitations of Telnet and Rlogin, these
+protocols do not support automated password authentication.
+
+\S2{plink-usage-options-user}\c{-l username} login with specified
+username
+
+As described in \k{plink-usage-batch}, you can specify the user name
+to log in as on the remote server using the \c{-l} option. For
+example, \c{plink login.example.com -l fred}.
+
+\S2{plink-usage-options-batch}\c{-batch} avoid interactive prompts
+
+If you use the \c{-batch} option, Plink will never give an
+interactive prompt while establishing the connection. If the
+server's host key is invalid, for example (see \k{gs-hostkey}), then
+the connection will simply be abandoned instead of asking you what
+to do next.
+
+This may help Plink's behaviour when it is used in automated
+scripts: using \c{-batch}, if something goes wrong at connection
+time, the batch job will fail rather than hang.
+
+\S2{plink-usage-options-cmdfile} \c{-m filename} read command from a
+file
+
+If the command you want to run on the remote server is particularly
+large, you can read it from a file using the \c{-m} option, instead
+of putting it directly on Plink's command line. On most Unix
+systems, you can even put multiple lines in this file and execute
+more than one command in sequence, or a whole shell script.
+
+\S2{plink-usage-options-portfwd} \c{-L} and \c{-R} set up port
+forwarding
+
+Plink allows you to use port forwarding just as PuTTY does; if you
+have set up a PuTTY saved session that specifies port forwardings,
+and you connect to that session using Plink, then the same port
+forwardings will be set up.
+
+For convenience, Plink also offers the option to set up port
+forwarding on the command line. The command-line options work just
+like the ones in Unix \c{ssh} programs.
+
+To forward a local port (say 5110) to a remote destination (say
+\cw{popserver.example.com} port 110), you can write:
+
+\c plink mysession -L 5110:popserver.example.com:110
+
+And to forward a remote port to a local destination, just use the
+\c{-R} option instead of \c{-L}:
+
+\c plink mysession -R 5023:mytelnetserver.myhouse.org:23
+
+For general information on port forwarding, see
+\k{using-port-forwarding}.
+
+\H{plink-batch} Using Plink in \i{batch files} and \i{scripts}
+
+Once you have set up Plink to be able to log in to a remote server
+without any interactive prompting (see \k{plink-usage-batch}), you
+can use it for lots of scripting and batch purposes. For example, to
+start a backup on a remote machine, you might use a command like:
+
+\c plink root@myserver /etc/backups/do-backup.sh
+
+Or perhaps you want to fetch all system log lines relating to a
+particular web area:
+
+\c plink mysession grep /~fjbloggs/ /var/log/httpd/access.log > fredlogs
+
+Any non-interactive command you could usefully run on the server
+command line, you can run in a batch file using Plink in this way.
+
+\H{plink-cvs} Using Plink with \i{CVS}
+
+To use Plink with CVS, you need to set the environment variable
+\c{CVS_RSH} to point to Plink:
+
+\c set CVS_RSH=\path\to\plink.exe
+
+You also need to arrange to be able to connect to a remote host
+without any interactive prompts, as described in
+\k{plink-usage-batch}.
+
+You should then be able to run CVS as follows:
+
+\c cvs -d :ext:user@sessionname:/path/to/repository co module
+
+If you specified a username in your saved session, you don't even
+need to specify the \q{user} part of this, and you can just say:
+
+\c cvs -d :ext:sessionname:/path/to/repository co module
+
+\H{plink-wincvs} Using Plink with \i{WinCVS}
+
+Plink can also be used with WinCVS. Firstly, arrange for Plink to be
+able to connect to a remote host non-interactively, as described in
+\k{plink-usage-batch}.
+
+Then, in WinCVS, bring up the \q{Preferences} dialogue box from the
+\e{Admin} menu, and switch to the \q{Ports} tab. Tick the box there
+labelled \q{Check for an alternate \cw{rsh} name} and in the text
+entry field to the right enter the full path to \c{plink.exe}.
+Select \q{OK} on the \q{Preferences} dialogue box.
+
+Next, select \q{Command Line} from the WinCVS \q{Admin} menu, and type
+a CVS command as in \k{plink-cvs}, for example: