AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have an rs/6000 running aix 4.3.3 that is listing stale/not wanted users when I type the command: who
Now, this machine underwent some maintenance earlier today to update the version of secure shell, but I still see users logged in with tty's that seem to be stale.
output from 'who':
user ttype May 22 18:46 (XX.XX.XX.XXX)
user ttypf May 22 18:46 (XX.XX.XX.XXX)
user ttyq0 May 22 18:46 (XX.XX.XX.XXX)
user ttyq1 May 22 18:46 (XX.XX.XX.XXX)
How would I manually boot this user off (assuming i have the root password, which i do)?? I am positive that this user is not in the middle of any activity and I want to avoid rebooting the entire machine for obvious downtime issues.
Try doing a 'ps -ef|grep ksh' (substitute what ever shell you are using for ksh if different). You'll have to weed through the result and get the process ID for their shell. You can then kill the session with a standard 'kill' command. Tack on a -9 if you are really malicious.
Run 'top' and look for the number of zombie processes. I've seen this before when a user's session IS a zombie process. If this is the case then the only correction is to reboot the system, or live with it.
machine load averages: 0.06, 0.08, 0.06 Sun May 23 16:50:22 2004
Cpu states: 0.0% user, 0.0% system, 0.0% wait, 100.0% idle
Real memory: 4193998.5M used, 305.6M free, 0.1M total
Virtual memory: 204.8M used, 0.0M free, 204.8M total
no-where does it state anything about zombie processes, as top typically does in linux.
It seemingly appears that the login's could be zombie processes...but is there anything I can check to positively identify these as such??
If you know which users you want to kick out , why dont you just run ps -ef|grep USERNAME and kill the ksh processes that they have?
You may have problems if the process refuses to die, which may happen.
Sorry, Zepplin, I was sleeping, I didn't see your post.
The answer is simple.
Type "who -u" instead of "who".
You will see the connected user and the PID of the father shell of each user.
Just kill -9 the PID appearing at the left (just before the system noame) and the user will be kicked out !