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.
After I run 'who' as root I receive the list of logged on users, tough some of these are not really logged. What could be misconfigured ? I'm under Fedora Core 2 and mostly using ssh 3.6 to remote connect. Thnx.
If you're using SSH to remote connect, as are other users, sometimes their sessions get disconnected yet SSH won't kill the session.
What you can do is either let init inherit the processes and reap them, or just setup your SSH config to kill off users that get disconnected or have not done anything on their sessions for a pre-determined amount of time.
Instead of "who", try using "w". It is a tad more informative, and it'll tell you how long someone's session has been inactive.
I've had it happen on my server where if I ran something within "screen", it left the user "logged in", and left a zombie process when it disconnected the screen.
You can go through and kill them manually (as I've found no way to avoid it if you have users improperly terminating sessions), or, if they've become zombies, let init reap them.
Also, while not the greatest practice, I just use "TCPKeepAlive yes". That seems to take care of when my PuTTY session gets whacked on accident.
Actually the table from 'who' is wrong, even with tcpkeepalive in sshd_config people are getting stuck and there are no processes to be killed...Guess it's the utmp file that's not being renewed, but why ? And how can I erase it ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.