@charlesrchance pushed 1 commit.
011dca2e5a07d76b46e86c7fa4ac4fbe3a5851a0 dispatcher: add option to retain
existing latency stats when reloading destinations
--
View it on GitHub:
https://github.com/kamailio/kamailio/pull/3534/files/852dc0848843b2886da3edfa9d1fd96c04e182aa..011dca2e5a07d76b46e
@charlesrchance pushed 1 commit.
852dc0848843b2886da3edfa9d1fd96c04e182aa dispatcher: add option to retain
existing latency stats when reloading destinations
--
View it on GitHub:
https://github.com/kamailio/kamailio/pull/3534/files/c91cf41c07a465715db41c6e5038853b53c923af..852dc0848843b2886da
### Description
I use debian 11 and Kamailio 5.6.x
modparam("htable", "htable",
"callpush=>size=10;autoexpire=86400;dbtable=callpush;dbmode=1")
I can store the values in the table, but if I shutdown kamailio, the current
values are not stored in the table.
Reproduction
Use a htable and
Thanks!
I agree...happy to make it the default if others think the same, but we never
quite know how it's already being used and who relies on a reload to actually
reset the stats.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3534#issuecommen
I have checkd `pcre2-config` config presence in the CentOS dists.
Looks like utility present in the CentOS 7, 8, 9 but does not exist.
Should you we drop CentOS 6 support?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3535#issuecomment-1671237494
Nice !
I am not sure this should be optional, I mean most if not all will want to
retain the stats.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3534#issuecomment-1671209534
You are receiving this because you are subscribed to this thread.
Me
Pre-Submission Checklist