[erlang-questions] disk_log question

Amit Murthy <>
Wed Apr 22 10:35:14 CEST 2009


Hi,

I want to use disk_log with an external format for application info logging.
I was experimenting with disk_log in the console and I found the following
behavior:

On an opened (opened via the open() call) log , once any of the functions in
the module return any, and I mean ANY error, the log gets closed and is no
longer available.
All subsequent calls return {error,no_such_log}.

Even an error like "** exception error: undefined function disk_log:xxxxx/2"
results in the same behavior.

I wanted to open a single log at startup and use it for logging in all the
other functions. Now, this may not be right way to do it, since if any of
the logging calls return an error, the log gets effectively closed.

Is there any explanation for this? Or is there a better way to implement
application error/info logging?

  Amit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20090422/6b3fd520/attachment.html>


More information about the erlang-questions mailing list