10-31-2017
It looks like the $SIG(signal_number) function in perl sets a signal catching function for the signal specified by signal_number. Since no such signal is every received by perl, that signal handler is never invoked.
As I said, I'm not fluent in perl, but it is obvious that the mechanism you're using is not designed to work that way in perl. You need to either find another way to do it in perl or extend perl to do what you want. Just making up a new signal name isn't going to magically make perl guess that a should send itself a signal (that the underlying operating system doesn't provide) before it is terminated by some other signal or by the user exiting the code perl is running.
Or, maybe you could convert your perl script to a shell script and use the shell command language's trap command to do what you want?
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
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 ,... (15 Replies)
Discussion started by: manas_ranjan
15 Replies
3. Shell Programming and Scripting
hi ,
What is the trap signal for "ENTER key"? (4 Replies)
Discussion started by: Sreejith_VK
4 Replies
4. Shell Programming and Scripting
Hi,
I have a trap problem when calling a child script in the background.
I know there are a lot of threads here on the issue of traps and signals, I think I have read all the relevant ones, but still haven't found an answer to my problem.
I'm working on Linux or HP, the script as you can see... (4 Replies)
Discussion started by: rimon
4 Replies
5. 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
6. 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
7. 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
8. 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
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. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
That is the last reply I received from my instructor, and I'm looking for some alternatives.
When using... (2 Replies)
Discussion started by: newuser45
2 Replies
killall(8) System Manager's Manual killall(8)
NAME
killall - Terminates all processes started by the user, except the calling process
SYNOPSIS
/usr/sbin/killall [- | [-]signal_name | -signal_number]
/usr/sbin/killall -l
FLAGS
The hyphen character (without an argument) sends a SIGTERM signal initially and then sends a SIGKILL signal to all processes that survive
for 30 seconds after receipt of the first signal. This gives processes that catch the SIGTERM signal an opportunity to clean up. A signal
name, optionally preceded by a hyphen, sends the specified signal to processes. The hyphen character (with a signal number argument) sends
the specified signal, either a name, stripped of the SIG prefix (such as KILL), or a number (such as 9). For information about signal
names and numbers, see the signal() system call.
In the System V habitat, the optional signal number does not have to be preceded with a hyphen (-). Lists signal names in numerical order
(as given in the /usr/include/signal.h file), stripped of the common SIG prefix.
DESCRIPTION
This command provides a convenient means of killing all processes created by the shell that you control. When started by the superuser,
the killall command kills all processes that can be terminated, except those processes that started it, the kernel processes, and processes
0 and 1 (init).
Security Configuration
This command is modified in all security configurations of the system.
EXAMPLES
To stop all background processes that have started, enter: killall This sends all background processes signal 9 (the kill signal, also
called SIGKILL). To stop all background processes, giving them a chance to clean up, enter: killall - This sends signal 15 (SIGTERM),
waits 30 seconds, and then sends signal 9 (SIGKILL). To send a specific signal to the background processes, enter: killall -2 This sends
signal 2 (SIGINT) to the background processes. To list the signal names in numerical order, stripped of the SIG prefix, enter: killall -l
This displays a list of signals, which may vary from system to system.
FILES
Specifies the command path
RELATED INFORMATION
Calls: kill(2), sigaction(2), signal(2) delim off
killall(8)