Please let me know wat the numbers shown in the above example does mean??
trap is a shell builtin which executes the command when the shell receives signals. In your example, the command would translate to 'dialog --msgbox "Script Aborted1" 6 50 ; error exit'. The signals translates to 1, 2, 3 and 15.
Hence whenever your script receives any of the signal 1, 2, 3 or 15, then a popup comes up with the message "Script Aborted1" and the script exits.
From man 7 signal, this is what the numbers stand for
The signals SIGKILL and SIGSTOP can not be trapped.
I'm using the trap command to capture any signals received whilst my script is running.
How's the best way of writing the signal and any other error messages to a file/error log' without having to type '2>$1' on the command line after the script name?
Cheers (3 Replies)
i have the following script that displays the current time until the user presses CTR + c.... but it does not work properly....
Something is not right with the trap command...
Help plz... :confused:
# script to continuously display current time.
# if script is terminated trap signal... (3 Replies)
Dear All
could you please explain me what does the trap command do and how I can write a program which can work as a trap command(in C Language). (1 Reply)
Could anybody tell me what the trap command does and how it performs the action it does. I had read the trap manual page but it is too concise that nothing is clear about it. Please tell how it works. (1 Reply)
Hi folks,
I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:....
The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Hello experts!
I need to know the use of trap command please
In one of our program we have trap "rm -f temp1 ; exit 1" 1 2 15 0
and program always exit with 1
there is a rm -f temp1 as well at the end of the program
as
rm -f temp1
exit 0
when I test a probram with set... (4 Replies)
I'm learning about the trap command from my bash book. I tried out the little script they gave:
trap "echo 'You hit control-C!' " INT
while true; do
sleep 60
done
But when I type control-c, the script just stops and the message is not displayed. I checked stty all and saw that control-c... (11 Replies)
dear all;
I can't under stand what does "trap" command do:
for example see below:
trap "echo; echo no interrupts >&2; sleep 3" 2 3 15
Plz , can any body explain the action of this command?
BR (3 Replies)
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)
Hi Folks -
For some reason, my trap command is not working. It's placed just prior to a normal exit:
#:: ------------------------------------------------------------------------
#::-- Script Name: LCM_Backup.sh
#::
#::-- Description: This script leverages Utility.sh to perform LCM... (16 Replies)
Discussion started by: SIMMS7400
16 Replies
LEARN ABOUT OSF1
pthread_kill
pthread_kill(3) Library Functions Manual pthread_kill(3)NAME
pthread_kill - Delivers a signal to a specified thread. (This routine is available only on a UNIX system.)
LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so)
SYNOPSIS
#include <pthread.h> #include <signal.h>
int pthread_kill(
pthread_t thread,
int sig);
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
IEEE Std 1003.1c-1995, POSIX System Application Program Interface
PARAMETERS
Thread to receive a signal request. A signal request.
DESCRIPTION
This routine sends a signal to the specified target thread thread. Any signal defined to stop, continue, or terminate will stop or termi-
nate the process, even though it can be handled by the thread. For example, SIGTERM terminates all threads in the process, even though it
can be handled by the target thread.
Specifying a sig argument of zero (0) causes this routine to validate the thread argument but not to deliver any signal.
The name of the "kill" routine is sometimes misleading, because many signals do not terminate a thread.
The various signals are as follows: SIGHUP, SIGPIPE, SIGTTIN SIGINT, SIGALRM, SIGTTOU SIGQUIT, SIGTERM, SIGIO SIGTRAP, SIGUSR1, SIGXCPU
SIGABRT, SIGSYS, SIGXFSZ SIGEMT, SIGURG, SIGVTALRM SIGFPE, SIGSTOP, SIGPROF SIGKILL, SIGTSTP, SIGINFO SIGBUS, SIGCONT, SIGUSR1 SIGSEGV,
SIGCHLD, SIGUSR2
If this routine does not execute successfully, no signal is sent.
RETURN VALUES
If an error condition occurs, this routine returns an integer value indicating the type of error. Possible return values are as follows:
Successful completion. The value of sig is invalid or unsupported signal value. The value of thread does not specify an existing thread.
ERRORS
None
RELATED INFORMATION
Manuals: Guide to DECthreads and Programmer's Guide
delim off
pthread_kill(3)