18 Mar
2024
18 Mar
'24
3:57 p.m.
```
version: kamailio 5.9.0-dev0 (x86_64/linux) 04a73a
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST,
DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC,
DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER,
USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_SEND_BUFFER_SIZE 262144,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 04a73a
compiled on 13:49:48 Mar 18 2024 with gcc 13.2.1
```
Tested with the above version (commit 04a73ace6572dd5c95a8f50b39b2ce712f7ebe84), and it no
longer gives the 500 error with `htable.seti`:
```
$ kamcmd htable.seti rconfig foo 1
Ok. Key set to new value.
$ kamcmd htable.get rconfig foo
{
item: {
name: foo
value: 1
flags: 0
expire: NEVER
}
}
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3774#issuecomment-2003838981
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3774/2003838981(a)github.com>