Sponsored Content
Operating Systems Linux How - Heapdump in Linux - kill -3 Post 302602924 by Corona688 on Tuesday 28th of February 2012 04:46:48 PM
Old 02-28-2012
Code:
$ man kill

KILL(1)                       Linux User's Manual                      KILL(1)



NAME
       kill - send a signal to a process

...

       0          0   n/a       exit code indicates if a signal may be sent
       ALRM      14   exit
       HUP        1   exit
       INT        2   exit
       KILL       9   exit      this signal may not be blocked
       PIPE      13   exit
       POLL           exit
       PROF           exit
       TERM      15   exit
       USR1           exit
       USR2           exit
       VTALRM         exit
       STKFLT         exit      may not be implemented
       PWR            ignore    may exit on some systems
       WINCH          ignore
       CHLD           ignore
       URG            ignore
       TSTP           stop      may interact with the shell
       TTIN           stop      may interact with the shell
       TTOU           stop      may interact with the shell
       STOP           stop      this signal may not be blocked
       CONT           restart   continue if stopped, otherwise ignore
       ABRT       6   core
       FPE        8   core
       ILL        4   core
       QUIT       3   core
       SEGV      11   core
       TRAP       5   core
       SYS            core      may not be implemented
       EMT            core      may not be implemented
       BUS            core      core dump may fail
       XCPU           core      core dump may fail
       XFSZ           core      core dump may fail

...

So yes.
This User Gave Thanks to Corona688 For This Post:
 

10 More Discussions You Might Find Interesting

1. 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

2. AIX

heapdump full the /

Hi everybody; Javaecore files and heapdump created every day in my system in the "/" and make it full. Is there any way to disable this core files or change there directory from the "/" to "/tmp". Note that AIX level is 5.2 with ML 6. BeSt ReGaRs (0 Replies)
Discussion started by: khalifah
0 Replies

3. UNIX for Dummies Questions & Answers

not able to kill find with kill -9

Hello everyone I am using HP Ux and had run a find command. Now I am trying to kill it with kill or kill -9 but it is not getting killed and still running. Any clues ? Thanks Sidhu (5 Replies)
Discussion started by: Amardeep
5 Replies

4. Programming

kill(0,-9) don't kill the process

Hi all i have simple c program , when i wish to kill the app im using kill(0,-9) , but it seams this command don't do any thing and the program. just ignore it . what im doing wrong here ? im using HP-UX ia64 Thanks (9 Replies)
Discussion started by: umen
9 Replies

5. Shell Programming and Scripting

Kill a process without using kill command

Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies

6. Linux

Kill a process without using kill command

I want to Kill a process without using kill command as i don't have privileges to kill the process. I know the pid and i am using Linux 2.6.9 OS. (6 Replies)
Discussion started by: sudhamacs
6 Replies

7. Solaris

How to analyze heapdump/coredump in solaris

Hello Friends, Need your help !! I have WebSphere Application Server 6 running on Solaris 10, some of my applications are facing out of memory errors. I have tried increasing the heapsize, still I am getting same messages randomly. I have used kill -3 <PID> to generate the... (1 Reply)
Discussion started by: sahilsardana
1 Replies

8. Shell Programming and Scripting

kill command in linux OS

How to undo the kill command in Linux OS? (9 Replies)
Discussion started by: poonam.gaigole
9 Replies

9. Solaris

Cannot kill a process with kill -9

Hello everyone, I have a process that I want to kill. I have tried kill-9 PID but it doesn't work. I have tried preap PID but it doesn't work too. The parent of my process is the process whose PID is 1, so I can't kill it. My OS is a Solaris 9. Can anyone help me understand what's going... (3 Replies)
Discussion started by: adilyos
3 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
SKILL(1)							Linux User's Manual							  SKILL(1)

NAME
skill, snice - send a signal or report process status SYNOPSIS
skill [signal to send] [options] process selection criteria snice [new priority] [options] process selection criteria DESCRIPTION
These tools are probably obsolete and unportable. The command syntax is poorly defined. Consider using the killall, pkill, and pgrep com- mands instead. The default signal for skill 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 -KILL. The default priority for snice is +4. (snice +4 ...) Priority numbers range from +20 (slowest) to -20 (fastest). Negative priority num- bers are restricted to administrative users. GENERAL OPTIONS
-f fast mode This is not currently useful. -i interactive use You will be asked to approve each action. -v verbose output Display information about selected processes. -w warnings enabled This is not currently useful. -n no action This only displays the process ID. -V show version Displays version of program. PROCESS SELECTION OPTIONS
Selection criteria can be: terminal, user, pid, command. The options below may be used to ensure correct interpretation. Do not blame Albert for this interesting interface. -t The next argument is a terminal (tty or pty). -u The next argument is a username. -p The next argument is a process ID number. -c The next argument is a command name. SIGNALS
The signals listed below may be available for use with skill. When known, numbers and default behavior are shown. Name Num Action Description 0 0 n/a exit code indicates if a signal may be sent ALRM 14 exit HUP 1 exit INT 2 exit KILL 9 exit this signal may not be blocked PIPE 13 exit POLL exit PROF exit TERM 15 exit USR1 exit USR2 exit VTALRM exit STKFLT exit may not be implemented PWR ignore may exit on some systems WINCH ignore CHLD ignore URG ignore TSTP stop may interact with the shell TTIN stop may interact with the shell TTOU stop may interact with the shell STOP stop this signal may not be blocked CONT restart continue if stopped, otherwise ignore ABRT 6 core FPE 8 core ILL 4 core QUIT 3 core SEGV 11 core TRAP 5 core SYS core may not be implemented EMT core may not be implemented BUS core core dump may fail XCPU core core dump may fail XFSZ core core dump may fail EXAMPLES
Command Description snice seti crack +7 Slow down seti and crack skill -KILL -v /dev/pts/* Kill users on new-style PTY devices skill -STOP viro lm davem Stop 3 users snice -17 root bash Give priority to root's shell SEE ALSO
killall(1), pkill(1), kill(1), renice(1), nice(1), kill(2), signal(7) STANDARDS
No standards apply. AUTHOR
Albert Cahalan <albert@users.sf.net> wrote skill and snice in 1999 as a replacement for a non-free version, and is the current maintainer of the procps collection. Please send bug reports to <procps-feedback@lists.sf.net>. Linux March 12, 1999 SKILL(1)
All times are GMT -4. The time now is 08:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy