Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You need the name of the process, but killall is a BAD solution to killing a single ssh login. The best way (if you want to do this) is to use "ps" to find the PID of their root bash session (listed as -bash, usually) and then kill -9ing it.
It's hard with ps to see who is connected to who..
Try netstat -tanp and locate the ESTABLISHED connection that matches.
The PID to kill is in the right hand column.
Don't use kill -9 if you can avoid it. It doesn't always allow the daemons to clean up temp files, locks etc. Use kill -TERM PID or kill -15 PID
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.