[asterisk-dev] [Code Review] 4604: loader/main: Don't set ast_fully_booted until deferred reloads are processed

[Corey Farrell]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4604/#review15154
-----------------------------------------------------------

Ship it!


Ship It!

- Corey Farrell


On April 9, 2015, 10:57 a.m., George Joseph wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/4604/
> -----------------------------------------------------------
> 
> (Updated April 9, 2015, 10:57 a.m.)
> 
> 
> Review request for Asterisk Developers and Corey Farrell.
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> Until we have a true module management facility it's sometimes necessary for one module to force a reload on another before its own load is complete.  If Asterisk isn't fully booted yet, these reloads are deferred.  The problem is that asterisk reports fully booted before processing the deferred reloads which means Asterisk really isn't quite ready when it says it is.
> 
> This patch moves the report of fully booted after the processing of the deferred reloads is complete.
> 
> 
> Diffs
> -----
> 
>   branches/13/main/loader.c 434447 
>   branches/13/main/asterisk.c 434447 
> 
> Diff: https://reviewboard.asterisk.org/r/4604/diff/
> 
> 
> Testing
> -------
> 
> Since the pjsip stack has the most number of related modules, I ran the channels/pjsip testsuite to make sure there aren't any issues.  All tests passed.
> 
> 
> Thanks,
> 
> George Joseph
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20150409/ae08f6d7/attachment.html>