liblognorm 2.0.5 released

Thursday, April 26th, 2018

We have just released liblognorm 2.0.5. This new version mainly provides a fix so liblognorm can build and work on Solaris systems. See the Changelog for details.

Version 2.0.5, 2018-04-26

  • bugfix: es_str2cstr leak in string-to v1 parser
    Thanks to Harshvardhan Shrivastava for the patch.
  • make “make check” “succeed” on solaris 10
    actually, we just ignore the CI failures so that OpenCSW can build
    new packages. The problems actually exist on that platform, but
    testing has shown they always existed. We currently run out of time
    to really fixing this, plus we never had any bug report on Solaris
    (I assme nobody uses it on Solaris 10). However, that issues is a
    blocker to make new rsyslog versions available on OpenCSW for
    Solaris 10, so we go the dirty way of pretenting there is no
    problem. Note: the issues was orignally not seen, as the failing
    tests have been added later on. So the problem was always there,
    just not visible.
  • some mostly cosmetic fixes detected by Coverity Scan
    e. g. memory leak if and only if system was completely out of memory

Download:
http://www.liblognorm.com/download/liblognorm-2-0-5/

As always, feedback is appreciated.

Best regards,
Florian Riedl

liblognorm 1.1.3 released

Monday, March 7th, 2016

We have just released liblognorm 1.1.3. This release contains support for libfastjson and now works on Solaris. See the Changelog for details.

Changelog:
Version 1.1.3, 2016-03-07

  • add support for libfastjson
  • make work on Solaris
  • check for runaway rules.
    A runaway rule is one that has unmatched percent signs and thus
    is not terminated properly at its end. This also means we no longer
    accept “rule=” at the first column of a continuation line, which is
    no problem (see doc for more information).
  • fix: process last line if it misses the terminating LF
    This problem occurs with the very last line of a rulebase (at EOF).
    If it is not properly terminated (LF missing), it is silently ignored.
    Previous versions did obviously process lines in this case. While
    technically this is invalid input, we can’t outrule that such rulebases
    exist. For example, they do in the rsyslog testbench, which made
    us aware of the problem (see https://github.com/rsyslog/rsyslog/issues/489 )
    I think the proper way of addressing this is to process such lines without
    termination, as many other tools do as well.
    closes https://github.com/rsyslog/liblognorm/issues/135

Download:
http://www.liblognorm.com/download/liblognorm-1-1-3/

As always, feedback is appreciated.

Best regards,
Florian Riedl