THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#232 - domain_attrs_table parameter not defined
User who did this - Juha Heinanen (jh)
Reason for closing: Fixed
Additional comments about closing: Exported domain_attrs_table variable.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=232
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi All,
I have just been testing xmlrpc on some of the IMS module RPC functions and
got some errors using nested structures. viz "{". Having a quick look
through the xmlrpc code show that it doesn't support nested structures in
the reply.
I am quite happy to fix this but am surprised that nobody has mentioned
this before as I see there are a few modules that use nested replies. Does
this maybe mean that XMLRPC is going to be deprecated (not a usual module)?
Cheers
Jason
gcc version 4.6.3 (Debian 4.6.3-1) gives the warning below that i don't
remember seeing with earlier gcc versions.
-- juha
CC (cc) [sip-proxy] msg_translator.o
msg_translator.c: In function ‘check_via_address’:
msg_translator.c:198:6: warning: variable ‘len’ set but not used [-Wunused-but-set-variable]
CC (cc) [M tls.so] tls_ct_wrq.o
In file included from tls_ct_q.h:35:0,
from tls_ct_wrq.h:35,
from tls_ct_wrq.c:32:
sbufq.h: In function ‘sbufq_add’:
sbufq.h:84:10: warning: variable ‘t’ set but not used [-Wunused-but-set-variable]
CC (cc) [M tls.so] tls_domain.o
In file included from tls_ct_q.h:35:0,
from tls_ct_wrq.h:35,
from tls_server.h:36,
from tls_domain.c:36:
sbufq.h: In function ‘sbufq_add’:
sbufq.h:84:10: warning: variable ‘t’ set but not used [-Wunused-but-set-variable]
tls_domain.c: In function ‘load_cert’:
tls_domain.c:418:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_domain.c: In function ‘load_ca_list’:
tls_domain.c:448:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_domain.c:455:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_domain.c: In function ‘load_crl’:
tls_domain.c:487:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_domain.c: In function ‘load_private_key’:
tls_domain.c:896:5: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_domain.c:904:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_domain.c:911:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_domain.c:911:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
CC (cc) [M tls.so] tls_dump_vf.o
CC (cc) [M tls.so] tls_init.o
In file included from tls_ct_q.h:35:0,
from tls_ct_wrq.h:35,
from tls_init.c:74:
sbufq.h: In function ‘sbufq_add’:
sbufq.h:84:10: warning: variable ‘t’ set but not used [-Wunused-but-set-variable]
CC (cc) [M tls.so] tls_mod.o
In file included from tls_ct_q.h:35:0,
from tls_ct_wrq.h:35,
from tls_server.h:36,
from tls_mod.c:64:
sbufq.h: In function ‘sbufq_add’:
sbufq.h:84:10: warning: variable ‘t’ set but not used [-Wunused-but-set-variable]
CC (cc) [M tls.so] tls_rpc.o
In file included from tls_ct_q.h:35:0,
from tls_ct_wrq.h:35,
from tls_server.h:36,
from tls_rpc.c:40:
sbufq.h: In function ‘sbufq_add’:
sbufq.h:84:10: warning: variable ‘t’ set but not used [-Wunused-but-set-variable]
sbufq.h:84:10: warning: variable ‘t’ set but not used [-Wunused-but-set-variable]
CC (cc) [M tls.so] tls_server.o
In file included from tls_ct_q.h:35:0,
from tls_ct_wrq.h:35,
from tls_server.h:36,
from tls_server.c:56:
sbufq.h: In function ‘sbufq_add’:
sbufq.h:84:10: warning: variable ‘t’ set but not used [-Wunused-but-set-variable]
tls_server.c: In function ‘tls_complete_init’:
tls_server.c:196:3: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_server.c: In function ‘tls_shutdown’:
tls_server.c:525:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_server.c: In function ‘tls_encode_f’:
tls_server.c:802:5: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_server.c:836:5: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_server.c: In function ‘tls_read_f’:
tls_server.c:1190:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
tls_server.c:1224:4: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
CC (cc) [M xmlrpc.so] xmlrpc.o
xmlrpc.c: In function ‘rpc_scan’:
xmlrpc.c:1457:6: warning: variable ‘fmt_len’ set but not used [-Wunused-but-set-variable]
CC (cc) [L libser_cds.so.0.1] rr_serialize.o
rr_serialize.c: In function ‘rr_dup’:
rr_serialize.c:10:6: warning: variable ‘res’ set but not used [-Wunused-but-set-variable]
CC (cc) [L libser_cds.so.0.1] serialize.o
serialize.c: In function ‘sstream_get_str_ex’:
serialize.c:91:6: warning: variable ‘res’ set but not used [-Wunused-but-set-variable]
CC (cc) [M pdt.so] domains.o
domains.c: In function ‘pdt_check_pd’:
domains.c:406:15: warning: variable ‘dhash’ set but not used [-Wunused-but-set-variable]
CC (cc) [M registrar.so] lookup.o
lookup.c: In function ‘lookup2’:
lookup.c:250:12: warning: variable ‘fp’ set but not used [-Wunused-but-set-variable]
CC (cc) [M usrloc.so] urecord.o
urecord.c: In function ‘nodb_timer’:
urecord.c:211:6: warning: variable ‘not’ set but not used [-Wunused-but-set-variable]
urecord.c: In function ‘wt_timer’:
urecord.c:254:6: warning: variable ‘not’ set but not used [-Wunused-but-set-variable]
urecord.c: In function ‘wb_timer’:
urecord.c:307:6: warning: variable ‘not’ set but not used [-Wunused-but-set-variable]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#227 - bug in s.replace?
User who did this - Jasmin Schnatterbeck (jasmin)
----------
Hi,
I have just noticed, that the following line sometimes also produces strange results (e.g. missing characters):
$var(ff_display)=$(var(ff_display){s.strip,1}{s.striptail,1});
Compared with the issue mentioned first:
$var pvs, more than one transformation, same pv changed
so it could be a bug in the code for $var pvs...
Jasmin
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=227#comment637
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Module: sip-router
Branch: master
Commit: b882818b0e82b8b286cbc6cd0e5c986db5b9fb51
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b882818…
Author: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Committer: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Date: Sun May 13 01:23:09 2012 +0100
modules_k/presence: Use non-pooled connections (where supported) when using notifier processes
- This helps with databases (such as PostgreSQL which is the only one that
currently supports specifying non-pooled connections) that create a server
process per client connection.
---
modules_k/presence/presence.c | 18 ++++++++++++------
1 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/modules_k/presence/presence.c b/modules_k/presence/presence.c
index a3e52c4..b960d5e 100644
--- a/modules_k/presence/presence.c
+++ b/modules_k/presence/presence.c
@@ -498,9 +498,12 @@ static int child_init(int rank)
LM_CRIT("child_init: database not bound\n");
return -1;
}
- if (pa_db)
- return 0;
- pa_db = pa_dbf.init(&db_url);
+ /* Do not pool the connections where possible when running notifier
+ processes. */
+ if (pres_notifier_processes > 0 && pa_dbf.init2)
+ pa_db = pa_dbf.init2(&db_url, DB_POOLING_NONE);
+ else
+ pa_db = pa_dbf.init(&db_url);
if (!pa_db)
{
LM_ERR("child %d: unsuccessful connecting to database\n", rank);
@@ -564,9 +567,12 @@ static int mi_child_init(void)
LM_CRIT("database not bound\n");
return -1;
}
- if (pa_db)
- return 0;
- pa_db = pa_dbf.init(&db_url);
+ /* Do not pool the connections where possible when running notifier
+ processes. */
+ if (pres_notifier_processes > 0 && pa_dbf.init2)
+ pa_db = pa_dbf.init2(&db_url, DB_POOLING_NONE);
+ else
+ pa_db = pa_dbf.init(&db_url);
if (!pa_db)
{
LM_ERR("connecting database\n");