[erlang-questions] ssl_esock leaking file descriptors

Ingela Andin ingela@REDACTED
Mon Sep 5 09:38:51 CEST 2011


Well the main problem with Erlang-implemented carriers are that when
the distribution is started the system is in such an early
stage that you can not start Erlang applications. The way we solved
this for ssl is that we have a special supervisor that we hook
into the kernel application  that will create a cloone of the ssl
application. The drawback with this is that you can not soft upgrade
the ssl-application
if you use ssl as distribution carrier (of course if you do not use
ssl for the distribution soft upgrade will be possible in R15).

Regards Ingela Erlang/OTP team - Ericssson AB

2011/9/3 Ulf Wiger <ulf.wiger@REDACTED>:
> On 2 Sep 2011, at 21:09, Ingela Andin wrote:
> Hi!
> In R15 you will be able to run the Erlang distrubution over the new
> ssl implementation.  The plan is also to drop the old ssl
> implementation in R15.
> Hmm, interesting…
> Does this also mean that it will be easier to define other carriers
> (erlang-implemented) for the Erlang distribution?
> BR,
> Ulf W
> Ulf Wiger, CTO, Erlang Solutions, Ltd.
> http://erlang-solutions.com
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list