[asterisk-bugs] [JIRA] (ASTERISK-25974) Unused realtime MOH classes not purged on 'moh reload'
Friendly Automation (JIRA)
noreply at issues.asterisk.org
Thu Apr 6 04:33:57 CDT 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236406#comment-236406 ]
Friendly Automation commented on ASTERISK-25974:
------------------------------------------------
Change 5319 merged by Joshua Colp:
Unused realtime MOH classes not purged on 'moh reload'
[https://gerrit.asterisk.org/5319|https://gerrit.asterisk.org/5319]
> Unused realtime MOH classes not purged on 'moh reload'
> ------------------------------------------------------
>
> Key: ASTERISK-25974
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25974
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_musiconhold
> Affects Versions: 11.22.0
> Environment: Linux 3.5.0-48-generic #72~precise1-Ubuntu SMP Tue Mar 11 20:09:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Sébastien Couture
> Severity: Minor
>
> Unused realtime MOH classes are not purged from memory when a 'moh reload' is issued _unless_ musiconhold.conf file is missing, invalid, or was modified (a simple 'touch' will suffice).
> Looking at the first few lines of code from the 'load_moh_classes()' function in res_musiconhold.c, you can see pretty clearly why we get this behaviour. That being said, it leaves out this specific scenario where you would expect realtime classes to be reloaded/purged whether musiconhold.conf was modified or not.
> cachertclasses=yes
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list