| Summary: | ASTERISK-24733: CLI "module reload cdr" does not handle an unchanged config file very well. | ||
| Reporter: | Richard Mudgett (rmudgett) | Labels: | |
| Date Opened: | 2015-01-28 14:03:56.000-0600 | Date Closed: | |
| Priority: | Major | Regression? | |
| Status: | Open/New | Components: | CDR/General |
| Versions: | 13.1.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) jira_asterisk_24733_example_v13.patch | |
| Description: | # Issuing a CLI "module reload cdr" when the {{cdr.conf}} file has not changed results in the {{No such module 'cdr'}} message.
# Issuing a CLI "config list" results in modules that use the config framework showing as core modules. # There are several core modules listed by CLI "config list" that should be handled by CLI "module reload x" that either need to be added to the {{reload_classes[]}} table or made to indicate that they are core and not reloadable. | ||
| Comments: | By: Richard Mudgett (rmudgett) 2015-01-28 14:07:36.804-0600 [^jira_asterisk_24733_example_v13.patch] - The patch points out in the code each of the problems listed in the issue description. The second issue about modules listed as core if they use the config framework has a simple fix implemented in the patch. | ||