Displaying messages in a remote node IO

Sean Hinde Sean.Hinde@REDACTED
Sun Dec 22 01:04:59 CET 2002

> It is better to have your own protocol for distributing log events to 
> a logger server on the remote node that does the actual io.           

Indeed. Or if you don't need to store the messages remotely just use the
functions in the error_logger module.

I suggest you reserve io:format for debugging - apart from anything else it
can be quite distracting typing commands into the shell of a live system
with errors flying through at a rate of knots!

More generally I suspect you will find that time spent digging through and
really digesting the documentation for SASL and the Design Principles will
be invaluable when you come to structure and build your real system. I did
this at the beginning, and whilst it is initially daunting you should find
that there really is an incredibly powerful structure hiding away in there
which will pretty much give you your whole system framework for free.


This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.

More information about the erlang-questions mailing list