[erlang-questions] Erlang/OTP 21.0-rc1 (Release Candidate)

[Jesper Louis Andersen]

I'm assuming that it is expected behavior that the 21-rc1 tarball was
removed from the downloads directory (The windows binaries are still there
btw, as is the README).

I found this because I ran `kerl update releases` and to my surprise it
wasn't there today, whereas in the weekend it was.

Is this an oversight, or should I await further development as things need
to move around some more?

On Mon, May 7, 2018 at 10:00 AM Lukas Larsson <lukas@REDACTED> wrote:

> Hello,
>
> On Fri, May 4, 2018 at 7:23 PM, Michał Muskała <michal@REDACTED> wrote:
>
>> The release looks great. Thank you to the whole OTP team for the work you
>> put into it.
>>
>
> Thanks!
>
>
>>
>> I wonder about the new file implementation that uses NIFs instead of
>> ports, specifically the instrumentation around it. With ports, there was a
>> way to list all ports and filter those that are files. This proved
>> sometimes useful in debugging situations. Would it be possible to also get
>> some kind of API to list all opened files, possibly with some additional
>> information (like path)?
>> I imagine a need for an API like that would be even more pressing once
>> sockets are ported to use NIFs instead of ports as well.
>>
>
> Yes, I also believe that something like this is going to be needed. While
> it is possible on most OSs to look in the /proc/ fs to see which files are
> opened, it is definitely useful to be able to track back to the process
> controlling it. Even more so for sockets.
>
> Personally I would prefer not to have to build something new within erts
> to handle this, but instead use what we have. Maybe ets tables that keeps
> track of files, connections, etc.
>
> Each sockets will most likely have to be associated with a process, so for
> them it could be possible to just store something in the process dictionary
> and let the debug process get the pdict of all processes.
>
> Lukas
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180508/9203344a/attachment.htm>