Sponsored Content
Top Forums Shell Programming and Scripting Continue Processing after a signal is caught Post 302917575 by Soham on Wednesday 17th of September 2014 03:11:36 PM
Old 09-17-2014
Continue Processing after a signal is caught

Is it possible to continue after signal is caught and control goes to function specified in the trap statement?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Signal Processing

Hello, Can any body give example of using Unix Signals. What I want to do is I am running a sql query in a shell script I want, if sql query exceed the defined no. of seconds limit, then I would like to kill the process. I know this can be done thru Unix Signal Handling but I do not know... (8 Replies)
Discussion started by: sanjay92
8 Replies

2. AIX

process caught signal 5

Hello, We are using AIX 5.2 ML 7. One of the process in its log file said the following and stopped running. Caught signal=5, exiting. What would cause the signal 5 to be generated on an AIX box. Please advise. Thx Jerardfjay (2 Replies)
Discussion started by: jerardfjay
2 Replies

3. Programming

Signal processing

We have written a deamon which have many threads. We are registering for the SIGTERM and trying to close main thread in this signal handling. Actually these are running on Mac OS X ( BSD unix). When we are unloading the deamon with command launchctl, it's sending SIGTERM signal to our process... (1 Reply)
Discussion started by: Akshay4u
1 Replies

4. Solaris

Solaris 10 install issue - "Caught Signal 11"

Rebuilding a server (T2000) from a flash archive I created on another server. Using a Solaris 10/08 DVD to boot from the was going to point it tot he flash archive and pull it over NFS. I've done this many times with success until now. It initially boots off the DVD, you input the... (5 Replies)
Discussion started by: Probos
5 Replies

5. Shell Programming and Scripting

How to continue in the loop after trapping signal

hi all.... plz tel me how can i solve this....here's the situation (just a sample!!).. $ cat sigtrap #!/usr/bin/perl $SIG{'INT'} = 'ABORT'; sub ABORT { print "\nStop the loop?? (y/n) : "; chop($ch=<STDIN>); if ($ch =~ //) { ... (3 Replies)
Discussion started by: tprayush
3 Replies

6. Solaris

Solaris 10 upgrade exiting ( caught signal 11)

Hi, I am pretty new to Solaris and am trying to upgrade from the OBP. I go through the process of booting from the cdrom, entering all necessary information and running the upgrade. The system completes analysis and then fail with the EXITING (caught signal 11) error I believe that... (5 Replies)
Discussion started by: Seanliam
5 Replies

7. Shell Programming and Scripting

Bypass getopts errors and continue processing?

Is there a way to do this? while getopts "n:g:m:i:p:d:a:" OPTION do case $OPTION in ... if i do a ./script.sh -n john -u user -p password, it will output: name= john ./script.sh: illegal option -- u Is there a way to skip over errors so that -p will get processed as well? By... (7 Replies)
Discussion started by: etranman1
7 Replies

8. Solaris

Solaris 10 "Exiting (caught signal 11)"

I get an error after the initializing screen. I am using a DVD/ROM to boot up the installation on a Dell Inspiron 1520. Segmentation fault - core dumped. I have tried to restart multiple times. Please help (1 Reply)
Discussion started by: Jimasaurus
1 Replies

9. Solaris

Exiting (caught signal 11)

I created a new Virtual machine and was trying to install Solaris but keep getting this error.:confused: EXITING (caught signal 11) Type "install-solaris to restart" Can't find anything on Google. This is the iso image I am using "sol-10-u11-ga-x86-dvd" Followed all the instructions on... (5 Replies)
Discussion started by: newborndba
5 Replies
abort(3C)																 abort(3C)

NAME
abort() - generate a software abort fault SYNOPSIS
DESCRIPTION
first closes all open files, streams, directory streams, and message catalogue descriptors, if possible, then causes the signal to be sent to the calling process. This may cause a core dump to be generated (see signal(2)). If the signal is caught, the handling function is executed. If the handling function returns, the action for is then reset to and the sig- nal is sent again to the process to ensure that it terminates. RETURN VALUE
does not return. ERRORS
No errors are defined. APPLICATION USAGE
is not intended to be caught. DIAGNOSTICS
If is neither caught nor ignored, and the current directory is writable, a core dump is produced and the message is written by the shell. SEE ALSO
adb(1), exit(2), kill(2), signal(2), signal(5), thread_safety(5). STANDARDS CONFORMANCE
abort(3C)
All times are GMT -4. The time now is 04:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy