Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
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