-\versionid $Id: plink.but,v 1.22 2004/04/24 12:25:08 jacob Exp $
+\define{versionidplink} \versionid $Id$
\C{plink} Using the command-line connection tool Plink
\c Usage: plink [options] [user@]host [command]
\c ("host" can also be a PuTTY saved session name)
\c Options:
-\c -V show version information
+\c -V print version information
\c -v show verbose messages
\c -load sessname Load settings from saved session
\c -ssh -telnet -rlogin -raw
-\c force use of a particular protocol (default SSH)
+\c force use of a particular protocol
\c -P port connect to specified port
\c -l user connect with specified username
\c -m file read remote command(s) from file
\c -C enable compression
\c -i key private key file for authentication
\c -s remote command is an SSH subsystem (SSH-2 only)
+\c -N don't start a shell/command (SSH-2 only)
Once this works, you are ready to use Plink.
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
+\c plink mysession grep /~fred/ /var/log/httpd/access.log > fredlog
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.