Sponsored Content
Full Discussion: Kill users
Top Forums Shell Programming and Scripting Kill users Post 55582 by samuel on Wednesday 15th of September 2004 06:37:12 AM
Old 09-15-2004
Thanx

Thanx everybody to help me....
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script to kill stranded/orphan process by users.

I have customers on our AIX/UNIX node startup a process that becomes stranded or orphaned and must be killed. I would like to create a script to check for these orphan processes and kill them. I can have cron run this job. The customers process will run and after 24 hours time out leaving an... (4 Replies)
Discussion started by: rjohnson
4 Replies

2. Shell Programming and Scripting

kill process of other users

Hi, Can I kill process submitted by another uesr (say user1) if I'm not the su. If I got some previledges granted from user1, can I kill user1's process? Please advise? Thank you very much! Regards, Tse (4 Replies)
Discussion started by: tsesukfan
4 Replies

3. HP-UX

Is there a script available to kill Idle users

My max user parm is set to 1050. I'm currently at 1038 this is causing major slow downs on the server. I looking for a way log off "idle" user logins with out having to do it individually. :confused: (5 Replies)
Discussion started by: rfmurphy_6
5 Replies

4. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Hi All, I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages. How can i terminate this daemon ? ? ? Regards, Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies

5. Shell Programming and Scripting

kill crashed out users

Hi all, We have a problem where we get a fair few users either exiting incorrectly or crashing. I'm trying to get a script together that runs every hour to kill these processes off. We are running Sco OperServer(TM) Release 5 The command we use to get a list of users who have crashed: ps... (2 Replies)
Discussion started by: tez
2 Replies

6. AIX

Script allows user to kill other users: I'd like to know HOW...

Hello list, Have a problem that's highlighting gaps in my knowledge; can you assist? We have a script that's tacked onto our trading application which allows branch managers etc. to kill off the sessions of other users at their branch. A menu option in the application spawns a shell running... (8 Replies)
Discussion started by: alexop
8 Replies

7. HP-UX

kill idle users

Hi, In my network we uses the NetTerm program to connect us to HP-UX 10.x server from windows workstations, but in some cases the user doesn't logout and close it by window's x button. The problem is that in HP-UX the user and all his tasks remain active and when he enter again HP-UX creates a... (12 Replies)
Discussion started by: efrenba
12 Replies

8. AIX

command to kill all loged in users

Guy's I'm looking for command to kill all the loged in users in AIX server Is there specific command can help us to kill any loged in users I have this command who -u it'll show me the process ID of all the users but I want command to kill all the users including to root without... (1 Reply)
Discussion started by: Mr.AIX
1 Replies

9. UNIX for Advanced & Expert Users

How to kill network users?

Hi everybody. I am using SCO open server. My problem is to kill users logged in my local network. I am using Kill -9 command for kill the repective user/terminal. But it shows in 'who -u'. when i try to kill agina that process it shows like "6229: no such process " User count is... (6 Replies)
Discussion started by: sanjaykunjam
6 Replies

10. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies
whodo(1M)						  System Administration Commands						 whodo(1M)

NAME
whodo - who is doing what SYNOPSIS
/usr/sbin/whodo [-h] [-l] [user] DESCRIPTION
The whodo command produces formatted and dated output from information in the /var/adm/utmpx and /proc/pid files. The display is headed by the date, time, and machine name. For each user logged in, device name, user-ID and login time is shown, followed by a list of active processes associated with the user-ID. The list includes the device name, process-ID, CPU minutes and seconds used, and process name. If user is specified, output is restricted to all sessions pertaining to that user. OPTIONS
The following options are supported: -h Suppress the heading. -l Produce a long form of output. The fields displayed are: the user's login name, the name of the tty the user is on, the time of day the user logged in (in hours:minutes), the idle time -- that is, the time since the user last typed anything (in hours:minutes), the CPU time used by all processes and their children on that terminal (in minutes:seconds), the CPU time used by the currently active processes (in minutes:seconds), and the name and arguments of the current process. EXAMPLES
Example 1 Using the whodo Command The command: example% whodo produces a display like this: Tue Mar 12 15:48:03 1985 bailey tty09 mcn 8:51 tty09 28158 0:29 sh tty52 bdr 15:23 tty52 21688 0:05 sh tty52 22788 0:01 whodo tty52 22017 0:03 vi tty52 22549 0:01 sh xt162 lee 10:20 tty08 6748 0:01 layers xt162 6751 0:01 sh xt163 6761 0:05 sh tty08 6536 0:05 sh ENVIRONMENT VARIABLES
If any of the LC_* variables ( LC_CTYPE, LC_MESSAGES, LC_TIME, LC_COLLATE, LC_NUMERIC, and LC_MONETARY ) (see environ(5)) are not set in the environment, the operational behavior of tar(1) for each corresponding locale category is determined by the value of the LANG environ- ment variable. If LC_ALL is set, its contents are used to override both the LANG and the other LC_* variables. If none of the above vari- ables is set in the environment, the "C" (U.S. style) locale determines how whodo behaves. LC_CTYPE Determines how whodo handles characters. When LC_CTYPE is set to a valid value, whodo can display and handle text and file- names containing valid characters for that locale. The whodo command can display and handle Extended Unix code (EUC) charac- ters where any individual character can be 1, 2, or 3 bytes wide. whodo can also handle EUC characters of 1, 2, or more col- umn widths. In the "C" locale, only characters from ISO 8859-1 are valid. LC_MESSAGES Determines how diagnostic and informative messages are presented. This includes the language and style of the messages, and the correct form of affirmative and negative responses. In the "C" locale, the messages are presented in the default form found in the program itself (in most cases, U.S. English). LC_TIME Determines how whodo handles date and time formats. In the "C" locale, date and time handling follow the U.S. rules. EXIT STATUS
The following exit values are returned: 0 Successful completion. non-zero An error occurred. FILES
/etc/passwd System password file /var/adm/utmpx User access and administration information /proc/pid Contains PID ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
ps(1), who(1), attributes(5), environ(5) SunOS 5.11 18 Jun 2003 whodo(1M)
All times are GMT -4. The time now is 10:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy