It seems as if you are getting error reports from the SASL application
(http://www.erlang.org/doc/man/sasl_app.html). If this is the case you
could either turn it off:
"The following configuration parameters are defined for the SASL
application. See app(4) for more information about configuration
parameters:
sasl_error_logger = Value <optional>
Value is one of:
tty
Installs sasl_report_tty_h in the error logger. This is the default
option.
{file,FileName}
Installs sasl_report_file_h in the error logger. This makes all reports
go to the file FileName. FileName is a string.
false
No SASL error logger handler is installed."
or you could replace it with one that is less verbose:
"The default simple handler is called alarm_handler and it may be
exchanged by calling gen_event:swap_handler/3 as
gen_event:swap_handler(alarm_handler, {alarm_handler, swap},
{NewHandler, Args}). NewHandler:init({Args, {alarm_handler, Alarms}}) is
called. Refer to gen_event(3) for further details."
bengt
> _______________________________________________
> erlang-questions mailing list
> erlang-q...@erlang.org
> http://www.erlang.org/mailman/listinfo/erlang-questions
_______________________________________________
erlang-questions mailing list
erlang-q...@erlang.org
http://www.erlang.org/mailman/listinfo/erlang-questions
> Hi All,
>
> I am a rank beginner, so please bear with me:
>
> I am fetching Web content from a set of URLs using http:request. For
> most of URLs everything works fine; however for some of them I see
> error reports on the console that look like so:
... tons of crap...
> ** Reason for termination ==
> ** session_remotly_closed
>
> As far as I can tell, session has been remotely closed.
that is indeed what's happening.
> I don’t mind a failure like this, but I would like to get rid of
> the error reports, as I am fetching many, many URLs.
it is a bizarre design decision to print an error report for a
perfectly normal event. there has been some complaining about this
on erlang-bugs (by me among others) to no avail.
The only sane solution (turning off sasl is insane) I've been able
to come up with is to patch; IIRC you have to replace the atom
'session_remotly_closed' with 'shutdown' in a few lines like this;
httpc_handler.erl: {stop, session_remotly_closed, State};
this looks like a "real" bug. handle_info/2 expects a to be handed a
record, but it gets an atom, namely 'request'. This will happens if
you type 'request' instead of 'Request' at the right place...
I'll CC this to erlang-bugs, in case the OTP guys miss it.
mats