Sponsored Content
Top Forums Shell Programming and Scripting Continue Processing after a signal is caught Post 302917580 by Soham on Wednesday 17th of September 2014 03:21:16 PM
Old 09-17-2014
Yes. I would like to come back and continue. The basic idea is to retry for three times and then error out.
 

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
EXINEXT(8)						      System Manager's Manual							EXINEXT(8)

NAME
exinext - Finding individual retry times SYNOPSIS
exinext address|message-id DESCRIPTION
A utility called exinext (mostly a Perl script) provides the ability to fish specific information out of the retry database. Given a mail domain (or a complete address), it looks up the hosts for that domain, and outputs any retry information for the hosts or for the domain. At present, the retry information is obtained by running exim_dumpdb (see below) and processing the output. For example: exinext piglet@milne.fict.example kanga.milne.fict.example:192.168.8.1 error 146: Connection refused first failed: 21-Feb-1996 14:57:34 last tried: 21-Feb-1996 14:57:34 next try at: 21-Feb-1996 15:02:34 roo.milne.fict.example:192.168.8.3 error 146: Connection refused first failed: 20-Jan-1996 13:12:08 last tried: 21-Feb-1996 11:42:03 next try at: 21-Feb-1996 19:42:03 past final cutoff time You can also give exinext a local part, without a domain, and it will give any retry information for that local part in your default domain. A message id can be used to obtain retry information pertaining to a specific message. This exists only when an attempt to deliver a message to a remote host suffers a message-specific error (see section 42.2). exinext is not particularly efficient, but then it isn't expected to be run very often. BUGS
This manual page needs a major re-work. If somebody knows better groff than us and has more experience in writing manual pages, any patches would be greatly appreciated. SEE ALSO
exim(8), /usr/share/doc/exim4-base/ AUTHOR
This manual page was stitched together from spec.txt by Andreas Metzler <ametzler at downhill.at.eu.org>, for the Debian GNU/Linux system (but may be used by others). March 26, 2003 EXINEXT(8)
All times are GMT -4. The time now is 09:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy