[erlang-questions] Binary data hiding sasl log entries?

[Youngkin, Rich]

I have some more information, and questions, regarding this.  First, the
number of "^@" characters is not in the thousands, it's in the millions and
represents most of the size of the file. This plays into the second item.
We're using logrotate and there seems to be a possible problem with that
(this is a fairly old post).

https://groups.google.com/forum/#!topic/comp.unix.solaris/Zc7ysjMGprQ

When we turned off logrotate for the sasl log the problem disappeared. So
this does indeed look like a bad interaction between logrotate and and the
process writing to the sasl log. Given that there are sasl settings
for *error_logger_mf_maxbytes
and **error_logger_mf_maxfiles, *I'm wondering if this is a known issue
with using logrotate with the sasl log, and/or if anyone else has run into
it?

http://www.erlang.org/doc/man/sasl_app.html

For now, we're going to switch from logrotate to the sasl log config
settings.

Thanks,
Rich

Hi all, I was wondering if anyone has seen binary data in a sasl log and
> what might
> be causing it. I'm seeing thousands and thousands of "^@" characters. In
> addition, I'm not seeing expected startup messages and I'm wondering if
> this info has been obscured by the binary data. I only see this occur at
> the beginning of a sasl log. I'm using R15B03. Thanks,
> Rich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150312/778d9cbd/attachment.htm>