02-20-2003
Tru, I have see a core dump in logn time...
Whay is this?
Whay thay disabled the generation of core files??
10 More Discussions You Might Find Interesting
1. Red Hat
Dear all
Can anyone tell me what commands I can run on a RedHat linux server to gain some diagnostic information, e.g. checking for disk errors or other related problems.
Regards (1 Reply)
Discussion started by: soliberus
1 Replies
2. Linux
hi all
I bought a new MSI motherboard and intel dual core processor .
i have currently installed fedora core 3 for which audio is not detected .
can u tell me which version of fedora core will support as i have tried with
fedora core 6 which gets installed but gives a error while... (0 Replies)
Discussion started by: nageshrk
0 Replies
3. Linux
Hi,
I want to know how to find out no of cores in linux.
I have given the command more /proc/cpuinfo
NOw I want to know what is diffrence between cpu cores and core id?
How to find out exact no of cores?
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. Shell Programming and Scripting
Dear all,
there are more than 10 files with .tar.gz extension in my folder i didnt want to extract them i just want to run the query to fetch my necessary data from all the files.
but when i run the command it untar the files in that folder.
gunzip -c abc.tar.gz | tar -xf - | grep REC |... (0 Replies)
Discussion started by: jojo123
0 Replies
5. UNIX for Dummies Questions & Answers
Sorry for the odd title, but I couldn't think of an easy way to describe my issue.
Background
I have a home security system that continually sends (via FTP) 4 different still images to a directory on my personal website - cam0.jpg, cam1.jpg, etc. I've written an extremely basic html script to... (4 Replies)
Discussion started by: CinciJeff
4 Replies
6. Shell Programming and Scripting
I have a bash file as following:
#!/bin/sh
deal_file(){
printf $1
printf "\t is a file"
echo
}
main(){
for file in `find "$1" `
do
deal_file $file
done
}
main $1
then I run ./t.sh .,get the following results: (1 Reply)
Discussion started by: 915086731
1 Replies
7. UNIX for Advanced & Expert Users
Does anyone know how to check linux stats per core? (1 Reply)
Discussion started by: cokedude
1 Replies
8. UNIX for Dummies Questions & Answers
I have seen commands like this: (hello is the executable file or maybe script file)
./hello
hello
.hello
So, anyone could tell me the differences among these commands? (2 Replies)
Discussion started by: icyfight
2 Replies
9. Shell Programming and Scripting
My task is to copy all files from many directories in one. The big problem i encounter is that some files in different directory have the same names. Is they are way to copy the files that have same names in a sub directory ( need to preserve the name of the files unchanged )
I have list with... (6 Replies)
Discussion started by: gogok_bg
6 Replies
10. Red Hat
what is the difference between Redhat Linux and Redhat Enterprise Linux. whereas Redhat linux have Server installation options too. (2 Replies)
Discussion started by: hananabbas
2 Replies
KILL(1) Linux User's Manual KILL(1)
NAME
kill - send a signal to a process
SYNOPSIS
kill [ -signal | -s signal ] pid ...
kill [ -L | -V, --version ]
kill -l [ signal ]
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 -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.
SIGNALS
The signals listed below may be available for use with kill. When known constant, 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 cannot be blocked
PIPE 13 exit
POLL exit
PROF exit
TERM 15 exit
USR1 exit
USR2 exit
VTALRM exit
STKFLT exit might not be implemented
PWR ignore might exit on some systems
WINCH ignore
CHLD ignore
URG ignore
TSTP stop might interact with the shell
TTIN stop might interact with the shell
TTOU stop might interact with the shell
STOP stop cannot 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 might not be implemented
EMT core might not be implemented
BUS core core dump might fail
XCPU core core dump might fail
XFSZ core core dump might fail
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
pkill(1), skill(1), kill(2), renice(1), nice(1), signal(7), killall(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.
Please send bug reports to <procps-feedback@lists.sf.net>
Linux November 21, 1999 KILL(1)