[Asterisk-Dev] Why use SIGABRT to kill mpg123 procs in res_musiconhold?

Sam Bingner sam at bingner.com
Thu Dec 11 22:04:57 MST 2003

I used SIGABRT because it worked better at killing off the child processes
than SIGTERM did.  Other signals were trapped by * somehow, if SIGTERM
works fine now and doesn't leave zombie mpg123's around, something may
have changed... Or I may have been smoking crack when I made that patch ;)


-----Original Message-----
From: asterisk-dev-admin at lists.digium.com
[mailto:asterisk-dev-admin at lists.digium.com] On Behalf Of Rich Adamson
Sent: Thursday, December 11, 2003 6:00 AM
To: asterisk-dev at lists.digium.com
Subject: Re: [Asterisk-Dev] Why use SIGABRT to kill mpg123 procs in

> On Wed, 2003-12-10 at 23:34, Tom Moertel wrote:
> > My * server's /var/lib/asterisk/mohmpg directory is littered with
> > core
> > files. After I little digging through the asterisk sources, I think I
> > know why. The function ast_moh_destroy() in res_musiconhold.c uses
> > SIGABRT to terminate mpg123 processes. Is there a reason for using
> > SIGABRT and not SIGTERM or SIGKILL instead?
> >

SIGTERM works fine here. Thanks for the help.


Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3243 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-dev/attachments/20031211/b2924294/smime.bin

More information about the asterisk-dev mailing list