[Asterisk-bugs] [Asterisk 0010139]: When removing a class from musiconhold.conf and reloading the module, the class is not removed from memory

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10139 
====================================================================== 
Reported By:                blitzrage
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10139
Category:                   Resources/res_musiconhold
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.6 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-06-2007 14:16 CDT
Last Modified:              07-06-2007 17:35 CDT
====================================================================== 
Summary:                    When removing a class from musiconhold.conf and
reloading the module, the class is not removed from memory
Description: 
This happens when loading from extconfig.conf as well, but since it happens
in the flatfile, I'll assume it's the same problem in both cases.

If I add a new class to musiconhold.conf, then run 'module reload
res_musiconhold.so' from the *CLI, then the class is added.

If I remove the class from the musiconhold.conf file, then reload
res_musiconhold.so, then the class is not removed from memory (only a
restart will remove it).
====================================================================== 

---------------------------------------------------------------------- 
 russell - 07-06-07 17:35  
---------------------------------------------------------------------- 
I don't doubt it, but it does seem like the right thing to do is to remove
ones that are no longer configured.  However, the code would also have to
take care not to remove it while it is still in use by any channels. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-06-07 17:35  russell        Note Added: 0066634                          
======================================================================