[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RaQ3i: Admins witch are "still logged in"
- Subject: Re: [cobalt-users] RaQ3i: Admins witch are "still logged in"
- From: "Rodolfo J. Paiz" <rpaiz@xxxxxxxxxxxxxx>
- Date: Fri Apr 6 14:41:11 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
At 4/5/01 04:15 PM +0200, you wrote:
After i had some broken connections (most with ssh) i found some admin users
witch are "still logged in" ==> see below.
[root@www admin]# who
admin pts/0 Apr 3 15:32 (gw.domain.ch)
admin pts/1 Apr 5 15:55 (gw.domain.ch)
admin pts/3 Apr 5 11:06 (gw.domain.ch)
admin pts/4 Mar 16 10:32 (gw.domain.ch)
admin pts/5 Apr 5 13:46 (gw.domain.ch)
First make sure you know which one *you* are, or you're going to end up
killing yourself.
This is a common problem when your session gets cut off; it happens to me
at least once a day. Do the following:
[root@www admin]# ps aux | grep pts
There will be several results there. Now,
[root@www admin]# kill -9 PID
where PID is the PID you want to kill. WARNING: the "-9" means
"immediately, no questions asked, whether it likes it or not." You *don't*
want to kill the wrong process with a -9, so use it with caution.
I think the PID's you should kill are those running bash. But you'll notice
that once you kill the "main" PID for pts/1, all others will go with it.
I'm just not sure which one that is. I log in as rpaiz, then su to whomever
I need to be, so I always just need to find the single "rpaiz" pts/? entry.
--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx