Hello, i would vote for dynamic allocation too. These days i had to allocate way more than default 4MB of pkg mem. Does anyone who used heavy MI loaded system with MI_SYSTEM_MALLOC compiled could give us feedback on how this feature is stable currently?

best regards, Antanas Masevicius On 2011.10.06 14:04, Daniel-Constantin Mierla wrote: > Hello, > > > > On 10/6/11 10:52 AM, Klaus Darilion wrote: >> Hi! >> >> Kamailio 1.3.4: "kamctl ul monitor" causes: >> >> ERROR:<core> [attr.c:80]: no more pkg mem (21) >> ERROR: mi_fifo [fifo_fnc.c:513]: command (ul_dump) processing failed >> >> There are ~ 2000 entries in location table. Default PKG size is used. >> >> I remember there were some similar reports recently, but couldn't >> find the relevant threads. >> >> Any hints for the cause of this problem and workarounds? > you can turn on usage of system memory manager for MI, see > lib/kmi/Makefile > > Maybe we should make it default. With the size of the config files > today, is not much left for other pkg operations, specially dumping > content via MI. > > Cheers, > Daniel >

Hello, On 10/6/11 10:52 AM, Klaus Darilion wrote: you can turn on usage of system memory manager for MI, see lib/kmi/Makefile Maybe we should make it default. With the size of the config files today, is not much left for other pkg operations, specially dumping content via MI.

On 06.10.2011 13:04, Daniel-Constantin Mierla wrote: What exactly causes the problem: the dump operation, MI or FIFO? Nowadays there are many other interface choices (RPC over FIFO, Unix ....). Is it possible to execute the commands (ul_dump ...) via other interface bypassing the MI_FIFO limitations?