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

[Max Lapshin]

Ok, I was using direct gen_event:   gen_event:add_sup_handler(error_logger,
Module, Config)

On Thu, May 3, 2018 at 4:29 PM, Lukas Larsson <lukas@REDACTED> wrote:

>
>
> On Thu, May 3, 2018 at 3:07 PM, Max Lapshin <max.lapshin@REDACTED> wrote:
>
>> Not sure about new logging:
>>
>> $ erl
>>
>> Erlang/OTP 21 [RELEASE CANDIDATE 1] [erts-10.0] [source] [64-bit]
>> [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe] [dtrace]
>>
>>
>> Eshell V10.0  (abort with ^G)
>>
>> 1> whereis(error_logger).
>>
>> undefined
>>
>> 2>
>>
>>
>> From http://erlang.org/documentation/doc-10.0-rc1/lib/
>> kernel-6.0/doc/html/error_logger.html  I do not see that error_logger is
>> no more with us.
>>
>> Is it a existing process or it is completely abandoned?
>>
>
> The error_logger event handler is started lazily when the first
> error_logger:add_report_handler call is done. So the new logging
> framework does not use the error_logger process, but it is started if
> legacy code uses it. All calls to error_logger:*_report/msg are redirected
> to logger which then decides what to do with them.
>
> Lukas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180503/86bbbad9/attachment.htm>