diff --git a/sources/tech/20170621 How To kill An Inactive OR Idle SSH Sessions.md b/sources/tech/20170621 How To kill An Inactive OR Idle SSH Sessions.md deleted file mode 100644 index 8409b66ac0..0000000000 --- a/sources/tech/20170621 How To kill An Inactive OR Idle SSH Sessions.md +++ /dev/null @@ -1,124 +0,0 @@ -wcnnbdk1 translating -How To kill An Inactive OR Idle SSH Sessions -============================================================ - -BY [MAGESH MARUTHAMUTHU][1] · PUBLISHED : JUNE 21, 2017 || LAST UPDATED: JUNE 21, 2017 - -Let’s imagine that you are working in server through ssh, for some reason your session get disconnected like, internet issue or power failure or your Local PC get rebooted, etc,. - -You may or mayn’t login to the server again to work but you have left the previous ssh session with out closing. - -How to Kill an inactive ssh sessions ? Identify the Inactive or Idle ssh sessions with help of `w` command, then get the idle session PID by issuing `pstree` command, finally kill the sessions using `kill` command. - -Suggested Read : [SSH Related Articles][2] - -Suggested Read : [Mosh (Mobile Shell) – Best Alternative for SSH to Connect Remote System][3] - -#### How to Identify Inactive or Idle SSH Sessions - -Login to the system and check how many user’s are currently logged in by issuing `w` command. If you identified your own session then note the Inactive or Idle ssh sessions to kill. - -In my scenario, I can see two users are currently logged in, one is my new ssh session which am currently running `w` command and another one for my idle session. - -``` -# w - 10:36:39 up 26 days, 20:29, 2 users, load average: 0.00, 0.02, 0.00 -USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT -root pts/0 219.91.219.14 10:34 28.00s 0.00s 0.00s -bash -root pts/2 219.91.219.14 10:36 0.00s 0.00s 0.00s w -``` - -#### How to Get a SSH Session PID - -To kill idle ssh session, we need a parent `PID` of the idle session. To get a parent pid, run the `pstree` command to see a tree diagram of all the processes. - -You also get the similar kind of output like below. The pstree command output is much bigger so, i removed many things from the file for better understanding. - -``` -# pstree -p -init(1)-+-abrtd(2131) - |-acpid(1958) - |-httpd(32413)-+-httpd(32442) - | - |-mingetty(2198) - |-mysqld_safe(24298)---mysqld(24376)-+-{mysqld}(24378) - | - |-php(32456)-+-php(32457) - | - |-sshd(2023)-+-sshd(10132)---bash(10136) - | `-sshd(10199)---bash(10208)---pstree(10226) - |-udevd(774)-+-udevd(2191) - `-udevd(27282) -``` - -From the above output, you can see the tree of sshd processes and branch’s. The main sshd process is `sshd(2023)` and two branch’s, `sshd(10132)` and `sshd(10199)`. - -As i told in the beginning of the article, one is my new session `sshd(10199)` because it shows the `pstree` command which is currently running by me, so the idle session is another one `sshd(10132)`. - -Suggested Read : [How to Access Secure Shell (SSH) Servers Through Standard Web Browsers][4] - -Suggested Read : [PSSH – Execute Commands on Multiple Linux Servers in Parallel][5] - -#### How to kill Idle SSH Sessions - -We got all the information about idle session. Now, i’m going to kill the idle session, using the `kill` command. Make sure you have replace your PID instead of us. - -``` - -# kill -9 10132 -``` - -#### Recheck whether the idle session get killed or not - -Again use `w` command to recheck whether the idle session get killed or not. Yes, it’s not there because i can see only one session which is owned by me. - -``` -# w - 10:40:18 up 26 days, 20:33, 1 user, load average: 0.11, 0.04, 0.01 -USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT -root pts/2 219.91.219.14 10:36 0.00s 0.00s 0.00s w -``` - -Suggested Read : [rtop – A Nifty Tool to Monitor Remote Server Over SSH][6] - -Suggested Read : [DSH – Run/Execute Shell Commands On Multiple Linux Servers At Once][7] - -#### Recheck with pstree Command - -Recheck once again with `pstree` command to double confirm it. Yes, only one ssh session is live which is owned by me. - -``` -# pstree -p -init(1)-+-abrtd(2131) - |-acpid(1958) - | - |-httpd(32413)-+-httpd(32442) - | - |-mingetty(2198) - |-mysqld_safe(24298)---mysqld(24376)-+-{mysqld}(24378) - | - |-php(32456)-+-php(32457) - | - |-sshd(2023)---sshd(10199)---bash(10208)---pstree(10431) - |-udevd(774)-+-udevd(2191) - `-udevd(27282) -``` - --------------------------------------------------------------------------------- - -via: http://www.2daygeek.com/kill-inactive-idle-ssh-sessions/ - -作者：[ Magesh Maruthamuthu][a] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]:http://www.2daygeek.com/author/magesh/ -[1]:http://www.2daygeek.com/author/magesh/ -[2]:http://www.2daygeek.com/category/ssh-tutorials/ -[3]:http://www.2daygeek.com/install-mosh-shell-ssh-client-in-linux-to-connect-remote-system/ -[4]:http://www.2daygeek.com/shellinabox-web-based-ssh-terminal-to-access-remote-linux-servers/ -[5]:http://www.2daygeek.com/pssh-parallel-ssh-run-execute-commands-on-multiple-linux-servers/ -[6]:http://www.2daygeek.com/rtop-monitor-remote-linux-server-over-ssh/ -[7]:http://www.2daygeek.com/dsh-run-execute-shell-commands-on-multiple-linux-servers-at-once/ diff --git a/translated/tech/20170621 How To kill An Inactive OR Idle SSH Sessions.md b/translated/tech/20170621 How To kill An Inactive OR Idle SSH Sessions.md new file mode 100644 index 0000000000..385ca06b25 --- /dev/null +++ b/translated/tech/20170621 How To kill An Inactive OR Idle SSH Sessions.md @@ -0,0 +1,123 @@ +如何关闭一个不活动的或者是空闲的 SSH 会话 +============================================================ + +作者 [MAGESH MARUTHAMUTHU][1] . 发布时间：2017年6月21日 || 最后更新：2017年6月21日 + +让我们来想像一下，当你通过 ssh 在服务器上工作时，由于网络、电源或者是本地 PC 重启等原因导致你断开你的连接会话。 + +你可能会再次登录服务器继续工作也可能不会但是你始终会留下之前没有关闭的 ssh 会话。 + +如何关闭一个不活动的 ssh 会话？首先使用 `w` 命令来识别出不活动或者是空闲的 ssh 会话，接着使用 `pstree` 命令来获取空闲会话的 PID，最后就是使用 `kill` 命令来关闭会话了。 + +建议阅读：[SSH 相关文章][2] + +建议阅读：[Mosh（Mobile Shell）- 最好的SSH 远程连接替代选项][3] + +#### 如何识别不活动的或者是空闲的 SSH 会话 + +登录系统通过 `w` 命令来查看当前有多少用户登录着。如果你识别出了自己的会话连接就可以记下其它不活动或者是空闲的 ssh 会话去关闭。 + +在我当前的例子中，能看见两个用户登录着，其中一个是我当前在执行 `w` 命令的 ssh 会话另一个就是之前的空闲会话了。 + +``` +# w + 10:36:39 up 26 days, 20:29, 2 users, load average: 0.00, 0.02, 0.00 +USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT +root pts/0 219.91.219.14 10:34 28.00s 0.00s 0.00s -bash +root pts/2 219.91.219.14 10:36 0.00s 0.00s 0.00s w +``` + +#### 如何获取 SSH 会话的 PID + +为了关闭空闲的 ssh 会话，我们需要空闲会话进程的父进程的 `PID`。（这里介绍另一个工具 pkill，使用 pkill -t pts/0 -kill 就可以关闭会话, debian8下可用，有些版本似乎需要更改-kill的位置）我们可以执行 `pstree` 命令来查看包括了所有进程的树状图，以便获取父进程的 pid。 + +你会获得与下方示例中相似的输出。pstree 命令的输出会比这个大得多，为了更好的理解我删去了许多不相关的内容。 + +``` +# pstree -p +init(1)-+-abrtd(2131) + |-acpid(1958) + |-httpd(32413)-+-httpd(32442) + | + |-mingetty(2198) + |-mysqld_safe(24298)---mysqld(24376)-+-{mysqld}(24378) + | + |-php(32456)-+-php(32457) + | + |-sshd(2023)-+-sshd(10132)---bash(10136) + | `-sshd(10199)---bash(10208)---pstree(10226) + |-udevd(774)-+-udevd(2191) + `-udevd(27282) +``` + +从上方的输出中，你可以看到 sshd 进程与分支的树形图。sshd 的主进程是 `sshd（2023）`，另两个分支分别为 `sshd（10132）` 和 `sshd（10199）`。 + +跟我在文章开始讲的相同，其中一个是我新的会话连接 `sshd（10199）` 它展示了我正在执行的 `pstree` 命令，因此空闲会话是另一个进程为 `sshd（10132）`。 + +建议阅读：[如何通过标准的网页浏览器来接入 Secure Shell (SSH) 服务器][4] + +建议阅读：[PSSH - 在多台 Linux 服务器上并行的执行命令][5] + +#### 如何关闭空闲 SSH 会话 + +我们已经获得了有关空闲会话的所有信息。那么，就让我们来使用 `kill` 命令来关闭空闲会话。请确认你将下方的 PID 替换成了你服务器上的空闲会话 PID。 + +``` + +# kill -9 10132 +``` + +#### 再次查看空闲会话是否已经被关闭 + +再次使用 `w` 命令来查看空闲会话是否已经被关闭。没错，只有那个我自己的当前会话还在，因此那个空闲会话已经被关闭了。 + +``` +# w + 10:40:18 up 26 days, 20:33, 1 user, load average: 0.11, 0.04, 0.01 +USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT +root pts/2 219.91.219.14 10:36 0.00s 0.00s 0.00s w +``` + +建议阅读：[rtop - 一个好用的通过 SSH 来监控远程服务器的工具][6] + +建议阅读：[DSH - 同时在多台 Linux 服务器上执行命令][7] + +#### 再次使用 pstree 命令检查 + +再次使用 `pstree` 命令确认。是的，只有那个我自己的 ssh 会话还在。 + +``` +# pstree -p +init(1)-+-abrtd(2131) + |-acpid(1958) + | + |-httpd(32413)-+-httpd(32442) + | + |-mingetty(2198) + |-mysqld_safe(24298)---mysqld(24376)-+-{mysqld}(24378) + | + |-php(32456)-+-php(32457) + | + |-sshd(2023)---sshd(10199)---bash(10208)---pstree(10431) + |-udevd(774)-+-udevd(2191) + `-udevd(27282) +``` + +-------------------------------------------------------------------------------- + +via: http://www.2daygeek.com/kill-inactive-idle-ssh-sessions/ + +作者：[ Magesh Maruthamuthu][a] +译者：[wcnnbdk1](https://github.com/wcnnbdk1) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]:http://www.2daygeek.com/author/magesh/ +[1]:http://www.2daygeek.com/author/magesh/ +[2]:http://www.2daygeek.com/category/ssh-tutorials/ +[3]:http://www.2daygeek.com/install-mosh-shell-ssh-client-in-linux-to-connect-remote-system/ +[4]:http://www.2daygeek.com/shellinabox-web-based-ssh-terminal-to-access-remote-linux-servers/ +[5]:http://www.2daygeek.com/pssh-parallel-ssh-run-execute-commands-on-multiple-linux-servers/ +[6]:http://www.2daygeek.com/rtop-monitor-remote-linux-server-over-ssh/ +[7]:http://www.2daygeek.com/dsh-run-execute-shell-commands-on-multiple-linux-servers-at-once/