Hello,
config parsing requires pkg to be initialized.
Also, for shm there are some internal triggers that can initialize it
(as it starts to be needed), so a matter of where is your shm_mem_size,
might no longer be used, so it safer to set shm size via cli param.
Cheers,
Daniel
On 05.09.23 08:49, Ivan Ribakov wrote:
> Is there any specific reason why shared memory can be configured via
> the config files ("shm_mem_size") AND CLI flags ("-m") but package
> memory can only be set via CLI flags ("-M")?
>
> Did no one ever came across the need to configure the package memory
> limit so far, or is there another way to achieve it without using the
> CLI flag?
>
> --
> Ivan Ribakov
> Software Engineer
> www.zaleos.net <http://www.zaleos.net/>
>
>
>
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
> Edit mailing list options or unsubscribe:
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy - Training Services -- asipto.com
Kamailio World Conference - kamailioworld.com
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
