Merged revisions 151905 via svnmerge from

https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r151905 | russell | 2008-10-25 05:59:02 -0500 (Sat, 25 Oct 2008) | 8 lines

Move AMI initialization to occur after loading modules.  This prevents a
deadlock when someone tries to initiate a module reload from the AMI just
as Asterisk is starting.

(closes issue #13778)
Reported by: hotsblanc
Fix suggested by hotsblanc

........


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@151906 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Russell Bryant
2008-10-25 11:02:11 +00:00
parent c74e85a23a
commit 316f3897a8

View File

@@ -3342,11 +3342,6 @@ int main(int argc, char *argv[])
ast_channels_init();
if (init_manager()) {
printf("%s", term_quit());
exit(1);
}
if (ast_cdr_engine_init()) {
printf("%s", term_quit());
exit(1);
@@ -3398,6 +3393,15 @@ int main(int argc, char *argv[])
exit(1);
}
/* AMI is initialized after loading modules because of a potential
* conflict between issuing a module reload from manager and
* registering manager actions. This will cause reversed locking
* order between the module list and manager actions list. */
if (init_manager()) {
printf("%s", term_quit());
exit(1);
}
dnsmgr_start_refresh();
/* We might have the option of showing a console, but for now just