08-31-2009
Hmm cfajohnson. How does the o/p stop the process without using kill ?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi there,
I have an application runnig on HP_UX which logs critical mesages to a log file.
What I would like to do is tail the log file and report on new messages. Easy....I here you say.
The log file is continuing to be written to and the check scritp will be executed from cron. I was... (2 Replies)
Discussion started by: nhatch
2 Replies
2. UNIX for Dummies Questions & Answers
Does anyone know how to redirect any messages sent to /dev/console to a file. Thanks in advance. (4 Replies)
Discussion started by: kdreaves
4 Replies
3. Shell Programming and Scripting
Hi,
I am new to perl. I want to write a perl script to monitor logs. Where i want to monitor exceptions logged or any kind of error strings. I have a dir(On Solaris) with multiple log file which keeps rolling to .gz file after some time in that same dir. These logs files size keeps on... (0 Replies)
Discussion started by: solitare123
0 Replies
4. Windows & DOS: Issues & Discussions
Hi,
I'd like to know if there is a way to monitor a log file conitnuously for one or more strings and if found, send an alarm. It should also take care not to inlcude the old log file entries.
Thanks. (2 Replies)
Discussion started by: er_ashu
2 Replies
5. Shell Programming and Scripting
Hi,
I ned to monitor the tomcat log file called "catalina.out" for "Out of memory" error.
the script should monitor this file and send us the mail as soon as it finds the string "Out of memory" in the file.
can ypu suggest me which is the best way to do this? (4 Replies)
Discussion started by: shivanete
4 Replies
6. UNIX for Dummies Questions & Answers
Hi,
Can anubody tell me how to log in to a remote server through console?
Your help is appreciated.. (5 Replies)
Discussion started by: Amol21
5 Replies
7. Red Hat
Hello All,
I'm facing the following problem:
On a specific server I have installed Red Hat ES 4.5 and everything seems ok.
But after a specific reboot, when the login prompt on the console, I put the root password and I canīt log on.
It is strange for me due to if y try to log on using SSH I... (1 Reply)
Discussion started by: mig28mx
1 Replies
8. Shell Programming and Scripting
Hi All;
I have a log file(dynamic) which i need to monitor; the format of the log
file is as follows
#Session ID STATUS
The status can be one of the three /starting ;/loading ;/success
Example
#Session ID STATUS
ABC /started.html
XYZ /started.html
ABC /loading.html
ABC... (2 Replies)
Discussion started by: maverick_here
2 Replies
9. Solaris
Hi,
I have been trolling thorugh vast numbers of information but have not yet found a solution to my problem.
I am unable to log onto my servers console and I can not explain whats going on.
I am running Solaris 10 and have a console connected to it via a kvm switch. I am able to see the... (2 Replies)
Discussion started by: philjt88
2 Replies
10. Shell Programming and Scripting
I have a menu based script where user will select different action via displayed menu.
I want to log all the action or say whatever displayed on screen to a log file and want to achieve with in the same script.
i tried named pipe as below..
logfile=mylogfile
mkfifo ${logfile}.pipe... (3 Replies)
Discussion started by: vidyadhar85
3 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)