<br><br><div class="gmail_quote">On Thu, Nov 5, 2009 at 7:35 AM, Kevin P. Fleming <span dir="ltr"><<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Olle E. Johansson wrote:<br>
<br>
> If I add a load= directive for a module in asterisk's modules.conf,<br>
> and it doesn't load Asterisk proceeds happily.<br>
> I would like a new statement where if Asterisk can't load the module<br>
> for some reason - bad config, bad compilation or something else,<br>
> Asterisk fails utterly and fails to start.<br>
<br>
</div>This should not be true; if the module's load_module() function returns<br>
AST_MODULE_LOAD_FAILURE, the loading process will be stopped and<br>
Asterisk will not continue starting up. The only way for the module to<br>
let Asterisk continue loading is for that function to return one of the<br>
other AST_MODULE_LOAD_<xxx> values.<br>
<br></blockquote><div>While my data is purely imperative, I haven't seen this occur. Every time I tell modules.conf to load something and it's "missing", Asterisk happily throws a warning in the log and CLI and keeps right on trucking. Is this relatively new?<br>
</div></div>