07-10-2007
Perderabo,
Sorry, but I don't think that's it. I did notice it was avoiding the built-in and I had a look at /usr/bin/kill - I should have posted the information but I don't like to bore people with a massive post which no one can be bothered reading...
-r-xr-xr-x 1 bin bin 7222 13 May 2004 /usr/bin/kill
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
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. Shell Programming and Scripting
Someone knows how do I kill a login user only with the login_name?
This moment I kill the user using the following command.
E4500:/mg98/samuel$ whodo samuel
Tue Sep 14 08:32:10 EST 2004
sun
pts/234 samuel 7:30
pts/234 24200 0:00 ksh
pts/234 26724 0:00 whodo... (3 Replies)
Discussion started by: samuel
3 Replies
4. HP-UX
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
5. Shell Programming and Scripting
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. HP-UX
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
7. UNIX for Dummies Questions & Answers
I am looking for a way to kill 2 processes from a user through some kind of script.
Using an oracle script, I get two process ids that need to be killed.
SQL> select ssn.process as client_process_id, pcs.spid as oracle_process_id, ssn.sid, ssn.serial#
2 from v$session ssn inner join... (5 Replies)
Discussion started by: Meert
5 Replies
8. Shell Programming and Scripting
Hi,
I am new to shell scripting and want to create a script with the follwoing description:
I want to restrict the users from giving a kill command on a unix server. The server have a restricted logins with login id and passwords. I want a script that will find out if a user has given a... (9 Replies)
Discussion started by: shell_scripting
9 Replies
9. UNIX for Advanced & Expert 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
Hi,
I have a situation where I want to ignore few users from list of users and print rest of user in log file.
say, I want to ignore aaa, bbb, ccc, ddd .. ppp from list of 20 user (do not want to include)
What is the good command or any script?
Thanks in advance. (1 Reply)
Discussion started by: sumit30
1 Replies
KILL(1) User Commands KILL(1)
NAME
kill - send a signal to a process
SYNOPSIS
kill [options] <pid> [...]
DESCRIPTION
The default signal for kill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP,
CONT, and 0. Alternate signals may be specified in three ways: -9, -SIGKILL or -KILL. Negative PID values may be used to choose whole
process groups; see the PGID column in ps command output. A PID of -1 is special; it indicates all processes except the kill process
itself and init.
OPTIONS
<pid> [...]
Send signal to every <pid> listed.
-<signal>
-s <signal>
--signal <signal>
Specify the signal to be sent. The signal can be specified by using name or number. The behavior of signals is explained in sig-
nal(7) manual page.
-l, --list [signal]
List signal names. This option has optional argument, which will convert signal number to signal name, or other way round.
-L, --table
List signal names in a nice table.
NOTES Your shell (command line interpreter) may have a built-in kill command. You may need to run the command described here as /bin/kill
to solve the conflict.
EXAMPLES
kill -9 -1
Kill all processes you can kill.
kill -l 11
Translate number 11 into a signal name.
kill -L
List the available signal choices in a nice table.
kill 123 543 2341 3453
Send the default signal, SIGTERM, to all those processes.
SEE ALSO
kill(2), killall(1), nice(1), pkill(1), renice(1), signal(7), skill(1)
STANDARDS
This command meets appropriate standards. The -L flag is Linux-specific.
AUTHOR
Albert Cahalan <albert@users.sf.net> wrote kill in 1999 to replace a bsdutils one that was not standards compliant. The util-linux one
might also work correctly.
REPORTING BUGS
Please send bug reports to <procps@freelists.org>
procps-ng October 2011 KILL(1)