#EXIT SSH SESSION PUTTY WINDOWS#

If you are Using PuTTY to log in to main and then using ssh to log into client, it isn't especially surprising that PuTTY's ^C is handled by main and not passed to client for top. If so it isn't clear why your SSH connection is in two parts (Win-PC -> 'main' -> 'client').

#EXIT SSH SESSION PUTTY WINDOWS#

Leaving you at a *nix shell prompt.įrom your mention of MobaXterm as an alternative to PuTTY I deduce you are using the Windows version of PuTTY not the *nix version of PuTTY. You suggest that an SSH session from *nix computer main to *nix computer client is dropped. Maybe you have a top alias or a top script earlier in $PATH than /usr/bin? $ type top If we look at we see this message can be produced if you have a script that uses trap SIGINT to intercept signals and perform special handling. So the question remains what is producing that message 'Killed by signal 2'. You can send any of these signals using the kill command but only one of them is a KILL signal and it isn't signal 2. Note that the KILL signal is signal 9 (not 2). SIGHUP 1 Term Hangup detected on controlling terminal Now lets check the numeric value of the interrupt signal $ man 7 signal The process exited because it received a signal 2, the interrupt signal SIGINT produced by Ctrl + Cįirst lets see what key combination corresponds to the interrupt signal $ stty -a | grep intr

That message isn't one you normally see but it is quite correct. I can't use 'Ctrl + C' combination because it sends kill signal to session.Ĭtrl + C is normally supposed to send an interrupt signal. I think so if we fix this route the problem will be solved. I think while I using MobaXterm the Ctrl+C has been sent to client server, while using PuTTy the interrupt signal has been sent to main server (so the ssh connection process). So the problem is not about servers configurations, it's about PuTTy configuration.

When I try MobaXterm for ssh there is no problem. 'ssh -vvv' output: Last login: Tue Feb 13 14:08:57 2018 from ~]# debug3: send packet: type 1ĭebug1: channel 0: free: client-session, nchannels 1ĭebug3: channel 0: status: The following connections are open: The output of this process is this: ~]# top //I use Ctrl + C to exit from ~]# Killed by signal 2. When I connect to a machine via ssh I can't use 'Ctrl + C' combination because of it sends kill signal to session.Īs an example, I start a SSH session to client machine from main machine, I run 'top' command on client and when I want to exit from 'top' I use 'Ctrl + C' combination and the SSH session closes.

Exit ssh session putty