3 Jul
2017
3 Jul
'17
6:08 p.m.
On 03.07.17 17:01, Sebastian Damm wrote:
Hi,
On Mon, Jul 3, 2017 at 4:22 PM, Daniel-Constantin Mierla
<miconda(a)gmail.com> wrote:
As I looked at code a bit
earlier, I noticed that it was silent (just
returning -1/false) when the locks set was not initialized. I pushed a
patch to log some error messages in this case, so people can become
aware what's going on.
Feel free to make a PR with enhancements to the docs.
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
Can you paste here the parameters for cfgutils
module related to locks?
Wow, that's what I missed. I didn't set any
parameter at all. I didn't
expect the locking to not work at all if I don't set it. I thought
there was a reasonable default value, which I only have to tune if
needed. After setting
modparam("cfgutils", "lock_set_size", 4)
the locking works as expected. Maybe that should be added to
documentation. I'll create a PR.
So I should set the size to something greater than the amount of
concurrent locks expected later? Is there a maximum?