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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14542 
====================================================================== 
Reported By:                jtodd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14542
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
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-02-24 13:56 CST
====================================================================== 
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.


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

---------------------------------------------------------------------- 
 (0100657) jtodd (administrator) - 2009-02-24 13:56
 http://bugs.digium.com/view.php?id=14542#c100657 
---------------------------------------------------------------------- 
Also worth mentioning:

I tried this, but same results:

#exec "/tmp/touchme.sh"

I also then tried this invalid test:

#exec blah

...and the results still were the same.  So this may not have anything to
do with the output of the script itself, but may be some deeper inherent
problem with either my incantation of the method or with the #exec code. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-24 13:56 jtodd          Note Added: 0100657                          
======================================================================