[asterisk-dev] tilghman: branch 1.4 r187428 - in /branches/1.4: include/asterisk/ main/

[Olle E. Johansson]

9 apr 2009 kl. 22.32 skrev Tilghman Lesher:

> On Thursday 09 April 2009 15:21:13 Olle E. Johansson wrote:
>> 9 apr 2009 kl. 22.13 skrev Tilghman Lesher:
>>> On Thursday 09 April 2009 14:59:59 Olle E. Johansson wrote:
>>>> Without looking into any of the two solutions, I just wanted to  
>>>> make
>>>> sure that you are aware that in manager 1.1 we have a module
>>>> management
>>>> manager action.
>>>
>>> While that will help with versions 1.6.0 and above, it will not
>>> solve the
>>> problem in 1.4.
>>
>> Right.
>> One alternative could be to merge the 1.4 version of that action
>> from my 1.4 moremanager branch and blacklist the command.
>
> I still think that detecting that race and failing the 'module  
> unload' command
> (executed on the command line, because 'module unload' is  
> blacklisted from
> AMI) is the better solution.  Changing how our users execute a  
> reload from AMI
> in the middle of a release cycle is EXTREMELY bad.

I agree that it would be EXTREMELY bad. Missed adding a ;-) marker on my
response. Sorry.


/O