silencing the error logger

Tuncer Ayaz tuncer.ayaz at
Sat Sep 11 17:51:48 EDT 2010

On Sat, Sep 11, 2010 at 6:41 PM, Ulf Wiger wrote:
> I added rebar to, but ended up
> generating my own 'rebar' file with some extra command-line options.
> The problem was that my QuickCheck suite starts and stops the
> gproc application, and getting 3000 printouts of the progress
> reports was pretty painful.
> Silencing the error_logger completely is surprisingly difficult.
> I ended up appending the following to line 2 in the rebar script:
>  -kernel error_logger silent -sasl errlog_type error
> (which should at least give you crash reports, but none of the
> progress reports.)
> I'm not sure that it would ever be a disadvantage to have those
> options there...

What about adding a rebar.config option and controlled by that do
> application:set_env(sasl, errlog_type, error)
> application:set_env(kernel, error_logger, silent)

If that works for you it has a higher chance of getting included than
modifying the escript invocation line for everybody.

More information about the rebar mailing list