-\versionid $Id: using.but,v 1.30 2004/09/20 22:06:29 jacob Exp $
+\versionid $Id: using.but,v 1.36 2004/10/19 13:54:50 jacob Exp $
\C{using} Using PuTTY
The following special commands are available in Telnet:
-\dt \I{Are You There, Telnet special command}Are You There
+\b \I{Are You There, Telnet special command}Are You There
-\dt \I{Break, Telnet special command}Break
+\b \I{Break, Telnet special command}Break
-\dt \I{Synch, Telnet special command}Synch
+\b \I{Synch, Telnet special command}Synch
-\dt \I{Erase Character, Telnet special command}Erase Character
+\b \I{Erase Character, Telnet special command}Erase Character
-\dt \I{Erase Line, Telnet special command}Erase Line
+\lcont{
+PuTTY can also be configured to send this when the Backspace key is
+pressed; see \k{config-telnetkey}.
+}
-\dt \I{Go Ahead, Telnet special command}Go Ahead
+\b \I{Erase Line, Telnet special command}Erase Line
-\dt \I{No Operation, Telnet special command}No Operation
+\b \I{Go Ahead, Telnet special command}Go Ahead
-\dd Should have no effect.
+\b \I{No Operation, Telnet special command}No Operation
-\dt \I{Abort Process, Telnet special command}Abort Process
+\lcont{
+Should have no effect.
+}
-\dt \I{Abort Output, Telnet special command}Abort Output
+\b \I{Abort Process, Telnet special command}Abort Process
-\dt \I{Interrupt Process, Telnet special command}Interrupt Process
+\b \I{Abort Output, Telnet special command}Abort Output
-\dt \I{Suspend Process, Telnet special command}Suspend Process
+\b \I{Interrupt Process, Telnet special command}Interrupt Process
-\dt \I{End Of Record, Telnet special command}End Of Record
+\lcont{
+PuTTY can also be configured to send this when Ctrl-C is typed; see
+\k{config-telnetkey}.
+}
-\dt \I{End Of File, Telnet special command}End Of File
+\b \I{Suspend Process, Telnet special command}Suspend Process
+
+\lcont{
+PuTTY can also be configured to send this when Ctrl-Z is typed; see
+\k{config-telnetkey}.
+}
+
+\b \I{End Of Record, Telnet special command}End Of Record
+
+\b \I{End Of File, Telnet special command}End Of File
In an SSH connection, the following special commands are available:
-\dt \I{Break, SSH special command}Break
+\b \I{IGNORE message, SSH special command}\I{No-op, in SSH}IGNORE message
-\dd Optional extension; may not be supported by server. PuTTY requests
-the server's default break length.
+\lcont{
+Should have no effect.
+}
-\dt \I{IGNORE message, SSH special command}\I{No-op, in SSH}IGNORE message
+\b \I{Break, SSH special command}Break
-\dd Should have no effect.
+\lcont{
+Only available in SSH-2, and only during a session. Optional
+extension; may not be supported by server. PuTTY requests the server's
+default break length.
+}
+
+\b \I{Signal, SSH special command}Signals (SIGINT, SIGTERM etc)
+
+\lcont{
+Only available in SSH-2, and only during a session. Sends various
+POSIX signals. Not honoured by all servers.
+}
\S2{using-newsession} Starting new sessions
\H{using-translation} Altering your \i{character set} configuration
If you find that special characters (\i{accented characters}, for
-example) are not being displayed correctly in your PuTTY session, it
-may be that PuTTY is interpreting the characters sent by the server
-according to the wrong \e{character set}. There are a lot of
-different character sets available, so it's entirely possible for
-this to happen.
+example, or \i{line-drawing characters}) are not being displayed
+correctly in your PuTTY session, it may be that PuTTY is interpreting
+the characters sent by the server according to the wrong \e{character
+set}. There are a lot of different character sets available, so it's
+entirely possible for this to happen.
If you click \q{Change Settings} and look at the \i{\q{Translation}
-panel}, you should see a large number of character sets which you
-can select. Now all you need is to find out which of them you want!
+panel}, you should see a large number of character sets which you can
+select, and other related options. Now all you need is to find out
+which of them you want! (See \k{config-translation} for more
+information.)
\H{using-x-forwarding} Using \i{X11 forwarding} in SSH
You should then tick the \q{Enable X11 forwarding} box in the
Tunnels panel (see \k{config-ssh-x11}) before starting your SSH
-session. The \q{X display location} box reads \c{localhost:0} by
-default, which is the usual display location where your X server
-will be installed. If that needs changing, then change it.
+session. The \q{X display location} box is blank by default, which
+means that PuTTY will try to use a sensible default such as \c{:0},
+which is the usual display location where your X server will be
+installed. If that needs changing, then change it.
Now you should be able to log in to the SSH server as normal. To
check that X forwarding has been successfully negotiated during
These options are not available in the file transfer tools PSCP and
PSFTP.
+\S2{using-cmdline-noshell} \I{-N-upper}\c{-N}: suppress starting a
+shell or command
+
+The \c{-N} option prevents PuTTY from attempting to start a shell or
+command on the remote server. You might want to use this option if
+you are only using the SSH connection for port forwarding, and your
+user account on the server does not have the ability to run a shell.
+
+This feature is only available in SSH protocol version 2 (since the
+version 1 protocol assumes you will always want to run a shell).
+
+This option is equivalent to the \q{Don't start a shell or command
+at all} checkbox in the SSH panel of the PuTTY configuration box
+(see \k{config-ssh-noshell}).
+
+These options are not available in the file transfer tools PSCP and
+PSFTP.
+
\S2{using-cmdline-compress} \I{-C-upper}\c{-C}: enable \i{compression}
The \c{-C} option enables compression of the data sent across the
projects / u / mdw / putty / blobdiff