09-22-2007
how to trap unix signal if the process killed/interupt occured in bash...
hey champs,
I have a process running.......i have to catch/trap the signal when the process is being interupted/killed (kill -9 pid) option......
how can i achieve the same thru my process........
let my process is a.sh and it supposed to take 13 mins to complete, but due to some problem , somebody killed that process a.sh using kill -9 <pid of a.sh>, so i want to log the message that process a.sh is killed ....
how can i achieve...
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Does anyone know how to program signals in fmli?
My fmli script goes in loop when the telnet session is closed. When I start the script from the prompt the issue do not happen. But when it is started by the login process it hags. That's why I want to program the SIGHUP to exit/finish the script.... (0 Replies)
Discussion started by: Marcos Brito
0 Replies
2. Shell Programming and Scripting
hi ,
What is the trap signal for "ENTER key"? (4 Replies)
Discussion started by: Sreejith_VK
4 Replies
3. UNIX for Dummies Questions & Answers
hi all ,
I want to execute a script on the user logout(using gnome environment).
Is ther any way to execute it through TRAP stmt? (2 Replies)
Discussion started by: harsha10
2 Replies
4. Shell Programming and Scripting
Hi all
I have Master script, Main script ,and 4 Child script.
Master.sh
#!/bin/bash
/export/home/user/Main.shMain.sh
#!/bin/bash
/export/home/user/Child1.sh &
/export/home/user/Child2.sh &
/export/home/user/Child3.sh &
/export/home/user/Child4.sh &I run only Master.sh script... (1 Reply)
Discussion started by: almanto
1 Replies
5. Shell Programming and Scripting
I just want to trap kill -9 signal issued by any of user from any terminal and just capture that user terminal who had raised this kill -9 command (1 Reply)
Discussion started by: puneet.goel
1 Replies
6. Shell Programming and Scripting
In my Bash script I have an exit/cleanup function in a trap statement like:
trap exitCleanup 1 2 3 6 15 25
Is there anyway to capture which signal # has occurred to record in a log file. Please note I am trying to avoid something like:
trap 'mySignal=1; exitCleanup' 1
trap... (1 Reply)
Discussion started by: ckmehta
1 Replies
7. Shell Programming and Scripting
Hi ,
i have a scenario where...i have to put a check where if script is executing more than 15mins i have to kill that script and n retry again 2nd time.
i this case i can use background process to do it but i feel trap will be the efficent way to do so...
but i dont know much about it... (1 Reply)
Discussion started by: crackthehit007
1 Replies
8. Linux
hey,
i have been facing a very fatel error with dovecot..
i am getting this error in my dovecot.log file
dovecot: Feb 13 15:21:02 Fatal: chdir(/var/mail/folders/user1) failed with uid 1001: Permission denied
dovecot: Feb 13 15:21:02 Error: child 18732 (imap) returned error 89
dovecot: Feb... (3 Replies)
Discussion started by: htshshrm2
3 Replies
9. Shell Programming and Scripting
Hi, I would like to ask, if is it possible to quit running loop in the script any other way than catching the trap signal. Ctrl-C ends only current running instance of process but not whole script. Any clues? (3 Replies)
Discussion started by: smoofy
3 Replies
10. Shell Programming and Scripting
Hi,
i have 2 machines in ESXI6 that both made a restart at the same time but no errors from ESXI side.
one machine with Centos 6.6 and one with centos 7
same log at the Dmesg:
please help me find a lead what could made this ?
Mar 17 20:20:28 pbxnl-b-sales-ru-ua init: tty (/dev/tty1) main... (2 Replies)
Discussion started by: batchenr
2 Replies
TKILL(1) LAM TOOLS TKILL(1)
NAME
tkill - Terminate LAM on one node.
SYNOPSIS
tkill [-dhvN] [-f killfile]
OPTIONS
-d Turn on debugging mode. This implies -v.
-h Print the command help menu.
-v Be verbose.
-N Pretend; do not take action.
-f killfile Use killfile as the name of the kill file.
DESCRIPTION
The tkill tool terminates the LAM session started by hboot(1) on the local node. tkill makes use of a kill file created by the LAM kernel,
which contains the process identifiers of every LAM process in ASCII format. A SIGHUP (see signal(3)) signal is sent to every process
listed in the kill file. tkill waits a short period of time for each process to die. By adding the debug option, the user can see the
final disposition of each process. The mission is accomplished if all processes end up dead.
In LAM, the first process to be killed is always the kernel. When the kernel receives its termination signal, it propagates the signal to
all of its constituent processes. Therefore, tkill will ordinarily be racing the kernel to kill all other processes. This redundant
aspect of tkill allows it to be used as a general purpose tool in association with hboot(1).
FILES
/tmp/lam-$USER@hostname the kill file, created by the kernel, where $USER is the userid, and hostname is the name of the local
machine
SEE ALSO
hboot(1), lam-helpfile(5)
LAM 7.1.4 July, 2007 TKILL(1)