| Summary: | ASTERISK-01406: [patch] Modules are not "reloaded" in same order as they are loaded. | ||
| Reporter: | Rob Gagnon (rgagnon) | Labels: | |
| Date Opened: | 2004-04-14 11:41:52 | Date Closed: | 2004-09-25 02:51:28 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) loader.c.patch.txt | |
| Description: | When you issue a reload command at the CLI. All modules are reloaded in reverse order from the order they were originally loaded. It seems to make sense to reload in the same order as a load in order to preserve any inter-module dependencies. ****** ADDITIONAL INFORMATION ****** Patch attached changes the method the linked list of module structs is originally created. Original code simply added references for loaded modules at head of linked-list. Patch changes this so that loaded module references are put at the end of the list. This allows the reload function to process without changes to it, but the list will be in opposite order. | ||
| Comments: | By: Rob Gagnon (rgagnon) 2004-04-14 13:42:14 quick note only to help keyword searches: loader.c By: Mark Spencer (markster) 2004-04-14 17:07:25 Fixed in CVS | ||