I agree with the idea of starting a new Janitor to update the modules to use '<module> reload' and change the behaviour of module reload to unload and load the module. This way, '<module> reload' should reparse the configuration file and 'module reload' should unload and load the module.
<br>Also, I think this should be documented in some doc for the sake of consistency to users and developers in future releases.<br><br>Best regards, Tomás.<br><br><div class="gmail_quote">On Nov 27, 2007 1:39 PM, Eliel Sardanons <
<a href="mailto:eliel@eliel.com.ar">eliel@eliel.com.ar</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">We could start a janitor for creating a 'foo reload' and we could make
<br>de 'module reload *.so' do a module unload; module load<br><div><div></div><div class="Wj3C7c"><br><br>On 11/27/07, Russell Bryant <<a href="mailto:russell@digium.com">russell@digium.com</a>> wrote:<br>> Kevin P. Fleming wrote:
<br>> > I would be surprised if any module's 'reload' command actually did much<br>> > of anything different than 'module reload' for the same module does, but<br>> > as BJ points out there certainly is no reason that they have to provide
<br>> > the same functionality.<br>><br>> They better not do anything different. :) If they do, I would definitely<br>> consider it a bug. That would be frustratingly inconsistent.<br>><br>> > I think adding a 'voicemail reload' command is a fine idea.
<br>><br>> Well, I guess I agree that it is fine because it is a bit more user friendly<br>> than "module reload app_voicemail.so". However, I don't think we can leave the<br>> conversation at that.
<br>><br>> The Asterisk CLI syntax got significantly switched around for Asterisk 1.4 for<br>> the sake of consistency. This issue points to another area where the Asterisk<br>> CLI is not consistent. We need to pick one way or the other and stick with it.
<br>> If people really like the idea of having individual reload CLI commands like<br>> "voicemail reload", then I say that we should:<br>><br>> 1) Start a janitor project to go through the code base and implement "foo
<br>> reload" CLI commands for _every_ module that implements a reload module callback<br>> function.<br>><br>> 2) Mark the "module reload res_foo.so" syntax as deprecated and eventually<br>> completely remove it. This syntax was always confusing to me when I started
<br>> with Asterisk, because I thought it was equivalent to "module unload / module load".<br>><br>> --<br>> Russell Bryant<br>> Senior Software Engineer<br>> Open Source Team Lead<br>> Digium, Inc.
<br>><br>> _______________________________________________<br>> --Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>><br>> asterisk-dev mailing list
<br>> To UNSUBSCRIBE or update options visit:<br>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>><br><br><br></div>
</div><font color="#888888">--<br>Eliel Sardañons<br></font><div><div></div><div class="Wj3C7c"><br>_______________________________________________<br>--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">
http://www.api-digital.com--</a><br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev
</a><br></div></div></blockquote></div><br>