[asterisk-dev] Unified Asterisk Interface
Tilghman Lesher
tilghman at mail.jeffandtilghman.com
Tue Dec 11 12:19:40 CST 2007
On Tuesday 11 December 2007 11:45:28 Steven Critchfield wrote:
> On Tue, 2007-12-11 at 10:53 -0600, Tilghman Lesher wrote:
> > On Tuesday 11 December 2007 10:16:31 Steven Critchfield wrote:
> > > On Tue, 2007-12-11 at 09:21 -0600, Tilghman Lesher wrote:
> > > > Well, if you're addicted to AGI, you're going to love 1.6, since
> > > > we've joined the boundary between live and dead mode and allowed an
> > > > AGI to make the transition.
> > >
> > > You mean we are going back to the earlier 1.4 days and before... Well
> > > the ability to not be killed when the transition is being made.
> >
> > No, you'll still get a HUP signal... but Asterisk will continue to
> > interact, should you survive that signal. Currently, after you get the
> > signal, Asterisk just waits for your process to die before exiting.
>
> So far even with test apps, I can't get an app to survive a hangup. This
> has caused us to stagnate on certain revisions of 1.4 and/or just use
> deadagi on newer revs.
In Perl, you just do: $SIG{HUP} = 'IGNORE'; at the top of your script.
> Fun thing is, I actually don't want to interact with asterisk after
> hangup, I just want to be able to survive long enough to clean up after
> myself.
Installing a signal handler will do precisely that.
--
Tilghman
More information about the asterisk-dev
mailing list