Hi Ping,
It's been fixed from this commit
https://github.com/OpenSIPS/opensips/commit/6a565b8b0baffd6a7ae53c65daaea468e0131c66.
The problem was some bad parsing of the input parameter which was
causing opening a pipe whether you set it or not, but it was not closed
unless the parameter was set. Thank you for reporting this bug!
Regards,
Ionut-Razvan Ionita
On 23.09.2015 16:50, Bogdan-Andrei Iancu wrote:
Hi Ping,
You mean actual files or file descriptors ? If you do a lsof, can you
see which file is kept open ? Also do you see any zombie OpenSIPS
processes (as a result of exec() call ) ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 16.09.2015 16:23, Ping Han wrote:
Hi,
I am having a problem using the "exec" function to run a curl
command. Every time the function is executed it opens a file and
never close it.
I have example config as follows. I am using Opensips 2.1.
------------------
$var = "http://myserver/var/tmp/test.php";;
exec("curl '$var(url)'", , "$var(out)");
------------------
This results in that the number of open files reaches the system
limit and the Opensips process crashes eventually. To workaround it I
have to restart Opensips whenever the number of open files reaches
75% of the system limit.
Has anyone seen the same issue? Is there any solution for this?
Thanks,
Ping
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
