search

siberian-fast-food / alogger

Simply the best logging framework for Erlang
Apache License 2.0
50 stars 16 forks source link

Application with alloger stop on alog_sup with Erlang R16 #37

Closed mkrentovskiy closed 11 years ago

mkrentovskiy commented 11 years ago

My application use alogger with the example configuration (tty + syslog).

On Erlang R15B3-1 all works fine. On Erlang R16B1 and R16B2 it stops on start when alog_sup starting. No information passed to syslog, erlang console also unacceptable.

Single syslog application works fine: 1> application:start(syslog). ok 3> {ok, S} = syslog:open("test", [cons, perror, pid], user). {ok,#Port<0.754>} 4> syslog:log(S, 1, "qwe123"). ok

But there are some warning in syslog compillation process: Compiling c_src/syslog_drv.c c_src/syslog_drv.c: In function ‘syslogdrv_control’: c_src/syslog_drv.c:187:13: warning: ‘driver_output_term’ is deprecated (declared at /home/mkrentovskiy/erlang/r16/erts-5.10.3/include/erl_driver.h:622) [-Wdeprecated-declarations] driver_output_term(port, term, sizeof term/sizeof *term); ^

Cy6erBr4in commented 11 years ago

The root cause is the erlang-syslog dependency, it hangs on syslog:open/3 call.