[asterisk-bugs] [Asterisk 0015189]: [patch] #exec script can't access manager on first asterisk load

Asterisk Bug Tracker noreply at bugs.digium.com
Fri May 29 00:01:22 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15189 
====================================================================== 
Reported By:                p_lindheimer
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15189
Category:                   Core/PBX
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     acknowledged
Target Version:             1.4.26
Asterisk Version:           SVN 
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 196616 
Request Review:              
====================================================================== 
Date Submitted:             2009-05-24 12:32 CDT
Last Modified:              2009-05-29 00:01 CDT
====================================================================== 
Summary:                    [patch] #exec script can't access manager on first
asterisk load
Description: 
In earlier versions of Asterisk (1.4.21.1 tested, also 1.2.x I believe), a
'#exec' directive in extensions.conf can run a script that can then access
the manager which is required to get to ASTDB to obtain information to
generate dialplan.

A fix to bug https://issues.asterisk.org/view.php?id=13778 (revision 151905) has
broken this.
====================================================================== 

---------------------------------------------------------------------- 
 (0105702) tilghman (administrator) - 2009-05-29 00:01
 https://issues.asterisk.org/view.php?id=15189#c105702 
---------------------------------------------------------------------- 
Another way to approach this is to add the ast_mutex_timedlock call,
similar to the way I added ast_rwlock_timedwrlock and
ast_rwlock_timedrdlock, and use that in ast_module_reload to avoid the
previous deadlock situation. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-29 00:01 tilghman       Note Added: 0105702                          
======================================================================




More information about the asterisk-bugs mailing list