Module: kamailio
Branch: master
Commit: 9834ed6ea815bfdb96e9889024c54a9b4b7b3b62
URL: https://github.com/kamailio/kamailio/commit/9834ed6ea815bfdb96e9889024c54a9…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2016-10-15T18:23:57+02:00
core: new command line option '-Y dir'
- set the runtime directory (used to create fifo, ctl socket, etc...)
---
Modified: main.c
---
Diff: https://github.com/kamailio/kamailio/commit/9834ed6ea815bfdb96e9889024c54a9…
Patch: https://github.com/kamailio/kamailio/commit/9834ed6ea815bfdb96e9889024c54a9…
---
diff --git a/main.c b/main.c
index 25d283c..cc976e0 100644
--- a/main.c
+++ b/main.c
@@ -188,8 +188,9 @@ Options:\n\
" -S disable sctp\n\
-Q Number of sctp child processes (default: equal to `-n')\n"
#endif /* USE_SCTP */
-" -V Version number\n\
+" -v (-V) Version number\n\
-h This help message\n\
+ -I Print more internal compile flags and options\n\
-b nr Maximum receive buffer size which will not be exceeded by\n\
auto-probing procedure even if OS allows\n\
-m nr Size of shared memory allocated in Megabytes\n\
@@ -200,6 +201,7 @@ Options:\n\
-g gid Change gid \n\
-P file Create a pid file\n\
-G file Create a pgid file\n\
+ -Y dir Runtime dir\n\
-O nr Script optimization level (debugging option)\n\
-a mode Auto aliases mode: enable with yes or on,\n\
disable with no or off\n\
@@ -1858,7 +1860,7 @@ int main(int argc, char** argv)
dprint_init_colors();
/* command line options */
- options= ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:"
+ options= ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:"
#ifdef STATS
"s:"
#endif
@@ -2051,6 +2053,7 @@ int main(int argc, char** argv)
case 'Q':
case 'a':
case 's':
+ case 'Y':
break;
case '?':
if (isprint(optopt)) {
@@ -2270,6 +2273,9 @@ int main(int argc, char** argv)
case 'w':
working_dir=optarg;
break;
+ case 'Y':
+ runtime_dir=optarg;
+ break;
case 't':
chroot_dir=optarg;
break;
Hi,
Given the presence of a global (e.g. "our") package variable in an
embedded Perl script used through app_perl, is there any implicit thread
safety?
That is to say, can a Perl function invoked by one SIP worker reset the
value of a global while another instance of the function invoked by a
different SIP worker is accessing it?
And if so, is it safe to use generic perlthr locking to avoid this?
Thanks!
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 (direct) / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
…ate copy of the msg
I've been facing recently some inconsistent replies generated from the two modules. Those replies didn't belong to the current request, but to some old transaction. The issue is due to the check made to decide if the current private copy of the message is consistent with the current transaction: due to memory reallocation there are chances that the check gives a false negative, bringing an old message to be used as a base for the reply. Using transaction's index and label is safer IMO.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/818
-- Commit Summary --
* modules/ims_auth, modules/ims_registrar_scscf: fix condition for private copy of the msg
-- File Changes --
M modules/ims_auth/pvt_message.c (13)
M modules/ims_auth/pvt_message.h (5)
M modules/ims_registrar_scscf/pvt_message.c (15)
M modules/ims_registrar_scscf/pvt_message.h (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/818.patchhttps://github.com/kamailio/kamailio/pull/818.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/818