[erlang-questions] noisy failures
Daniil Churikov
ddosia@REDACTED
Thu Apr 3 09:33:29 CEST 2014
Here is my relx.config:
{release, {app_name, "0.0.1"}, [app_name,
sasl]}.
{extended_start_script,
true}.
If you add sasl, you can see more verbose logs in _rel/log/ directory
On Wednesday, April 2, 2014 3:59:17 PM UTC+4, t x wrote:
>
> Hi,
>
>
> ## context:
>
> * I'm using erlang.mk + relx
>
> * I'm running my erlang apps as one of the following:
> _rel/bin/app_name start
> _rel/bin/app_name console
>
> * what I like about "_rel/bin/app_name start" <-- I feel like this
> is the right way for production use
>
> * what I like about "_rel/bin/app_name console" <-- I get noisy
> failures (i.e. when something goes wrong, it floods stdout
>
>
> ## what I want:
>
> I want to use "_rel/bin/app_name start", yet get the same level of
> errors/warnings/assertions as I do when I run it as "_rel/bin/app_name
> console"
>
>
> ## what I have tried:
>
> * _rel/bin/app_name start
> * _rel/bin/app_name remote_console
>
> However, "start + remote_console" does not seem to get me the same
> amount of errors as I do from "console".
>
>
> ## question:
>
> Is there a wya to use start + remote_console, yet get the same level
> of errors / warnings as with "console"?
>
> Thanks!
> _______________________________________________
> erlang-questions mailing list
> erlang-q...@REDACTED <javascript:>
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140403/20deec89/attachment.htm>
More information about the erlang-questions
mailing list