Skip to content
Snippets Groups Projects
  1. Jun 09, 2009
    • David Vossel's avatar
      module load priority · d532cbcd
      David Vossel authored
      This patch adds the option to give a module a load priority. The value represents the order in which a module's load() function is initialized.  The lower the value, the higher the priority.  The value is only checked if the AST_MODFLAG_LOAD_ORDER flag is set.  If the AST_MODFLAG_LOAD_ORDER flag is not set, the value will never be read and the module will be given the lowest possible priority
      on load.  Since some modules are reliant on a timing interface, the timing modules have been given a high load priorty.
      
      (closes issue #15191)
      Reported by: alecdavis
      Tested by: dvossel
      
      Review: https://reviewboard.asterisk.org/r/262/
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@199743 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      d532cbcd
  2. Jun 08, 2009
  3. Jun 07, 2009
  4. Jun 06, 2009
  5. Jun 05, 2009
  6. Jun 04, 2009
    • David Vossel's avatar
      Merged revisions 199138 via svnmerge from · e018606c
      David Vossel authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
        r199138 | dvossel | 2009-06-04 14:00:15 -0500 (Thu, 04 Jun 2009) | 3 lines
        
        Additional updates to AST-2009-001
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@199139 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      e018606c
    • Eliel C. Sardanons's avatar
      Move static docs to the new AstXML form. · 9ce385bd
      Eliel C. Sardanons authored
      Move SMDI_MSG and SMDI_MSG_RETRIEVE functions statis documentation
      to XML.
      
      (issue #15245)
      Reported by: eliel
      Patches:
            res_smdi_static_conversion.txt uploaded by lmadsen (license 10)
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@199091 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      9ce385bd
    • Sean Bright's avatar
      Merged revisions 199022 via svnmerge from · befad108
      Sean Bright authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
        r199022 | seanbright | 2009-06-04 10:14:57 -0400 (Thu, 04 Jun 2009) | 40 lines
        
        Safely handle AMI connections/reload requests that occur during startup.
        
        During asterisk startup, a lock on the list of modules is obtained by the
        primary thread while each module is initialized.  Issue 13778 pointed out a
        problem with this approach, however.  Because the AMI is loaded before other
        modules, it is possible for a module reload to be issued by a connected client
        (via Action: Command), causing a deadlock.
        
        The resolution for 13778 was to move initialization of the manager to happen
        after the other modules had already been lodaded.  While this fixed this
        particular issue, it caused a problem for users (like FreePBX) who call AMI
        scripts via an #exec in a configuration file (See issue 15189).
        
        The solution I have come up with is to defer any reload requests that come in
        until after the server is fully booted.  When a call comes in to
        ast_module_reload (from wherever) before we are fully booted, the request is
        added to a queue of pending requests.  Once we are done booting up, we then
        execute these deferred requests in turn.
        
        Note that I have tried to make this a bit more intelligent in that it will not
        queue up more than 1 request for the same module to be reloaded, and if a
        general reload request comes in ('module reload') the queue is flushed and we
        only issue a single deferred reload for the entire system.
        
        As for how this will impact existing installations - Before 13778, a reload
        issued before module initialization was completed would result in a deadlock.
        After 13778, you simply couldn't connect to the manager during startup (which
        causes problems with #exec-that-calls-AMI configuration files).  I believe this
        is a good general purpose solution that won't negatively impact existing
        installations.
        
        (closes issue #15189)
        (closes issue #13778)
        Reported by: p_lindheimer
        Patches:
              06032009_15189_deferred_reloads.diff uploaded by seanbright (license 71)
        Tested by: p_lindheimer, seanbright
        
        Review: https://reviewboard.asterisk.org/r/272/
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@199051 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      befad108
  7. Jun 03, 2009
  8. Jun 02, 2009
  9. Jun 01, 2009
Loading