[asterisk-bugs] [Asterisk 0014542]: #exec lines causing failure of parsing of extensions.conf

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Sep 1 12:35:13 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14542 
====================================================================== 
Reported By:                jtodd
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14542
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 178303 
Request Review:              
====================================================================== 
Date Submitted:             2009-02-24 13:47 CST
Last Modified:              2009-09-01 12:35 CDT
====================================================================== 
Summary:                    #exec lines causing failure of parsing of
extensions.conf
Description: 

If I add an #exec line with a script to my extensions.conf, Asterisk locks
up when it tries to parse that line and include the data from the script. 

I've included a scripted capture of the #exec'ed file, the output, and the
fact that I have to kill Asterisk with "-9" to get it to die.


====================================================================== 

---------------------------------------------------------------------- 
 (0109900) jtodd (administrator) - 2009-09-01 12:35
 https://issues.asterisk.org/view.php?id=14542#c109900 
---------------------------------------------------------------------- 
I'm trying with "asterisk -vvvvgcd" as a standalone startup, which causes a
lock.  Still a problem here.

Removing the "#exec" line from extensions.conf results in Asterisk
executing completely and successfully with the same command. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-01 12:35 jtodd          Note Added: 0109900                          
======================================================================




More information about the asterisk-bugs mailing list