Skip to main content

How to log someone out of ssh terminal session

How to: Log someone out of the ssh terminal session but yourself? Kick off other users from linux terminal? Kill someone's ssh session?

First of all find who is logged in the system:
[root@testlinux /]# who
root :0 2012-04-05 10:58
root pts/1 2012-04-05 11:08 (:0.0)
root pts/2 2012-04-26 13:46 (192.168.1.100)
root pts/3 2012-04-17 17:08 (192.168.1.200)

Which one is my terminal session process?
[root@testlinux /]# echo $SSH_TTY
/dev/pts/3
pts 3 is me.

Find ssh terminal session process id to kill:
[root@testlinux /]# ps -ef |grep sshd
root  2857  1  0  Apr05  ?  00:00:00  /usr/sbin/sshd
root  13739  2857  0  13:46  ?  00:00:00  sshd: root@pts/2
root  13767  26213  0  13:50  pts/3  00:00:00  grep sshd
root  26211  2857  0  Apr17  ?  00:00:02  sshd: root@pts/3

Kill pts2's ssh session:
[root@testlinux /]# kill -9 13739
Etiketler:

Comments

Post a Comment

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three
Post a Comment
Read more

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) 192.168.1.11 Slave1 Node: (Centos 7.2) 192.168.1.12 Slave2 Node: (Centos 7.2) 192.168.1.13 Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/multi-user.target.wants/redis-server.service Each Node: /etc/
1 comment
Read more