| Summary: | ASTERISK-23136: cel.conf is read by more than one core module. | ||
| Reporter: | Richard Mudgett (rmudgett) | Labels: | |
| Date Opened: | 2014-01-13 11:11:39.000-0600 | Date Closed: | 2017-12-18 10:59:52.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | CEL/cel_manager CEL/General |
| Versions: | 1.8.25.0 11.7.0 12.0.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | In v1.8 and v11 cel.conf is read unconditionally in the main CEL module and conditionally on reload in cel_manager. A simple fix for these versions is to not read the config file conditionally on reloads.
In v12 cel.conf is read by the config framework (conditionally on reload) and conditionally on reload in cel_manager. The cel_manager module needs to get its own config file. Because multiple modules read the same config file and read it conditionally for reloads, the modules reading the config file conditionally might not reload the config when they should. | ||
| Comments: | By: Richard Mudgett (rmudgett) 2014-06-20 20:10:06.469-0500 Hmm. After working on the config file cache for another problem, this may not really be a problem. The cache keeps track of the requesting module as well as the file loaded. Will need more investigation to be sure this is really a problem. By: Joshua C. Colp (jcolp) 2017-12-18 10:59:52.166-0600 I've looked over the code in question and I don't believe this is a problem. | ||