liblognorm

Tag: libfastjson

  • liblognorm 2.0.1 released

    We have just released liblognorm 2.0.1. This new version provides some fixes for the public headers als well as issues in pkgconfig file. Also it requires libfastjson (>=0.99.3) instead of json-c. See the Changelog for details.

    Changelog:
    Version 2.0.1, 2016-08-01

    • fix public headers, which invalidly contained a strndup() definition
      Thanks to Michael Biebel for this fix.
    • fix some issues in pkgconfig file
      Thanks to Michael Biebel for this fix.
    • enhance build system to natively support systems with older autoconf versions and/or missing autoconf-archive. In this case we gracefully degrade functionality, but the build still is possible. Among others, this enables builds on CentOS 5.

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

    As always, feedback is appreciated.

    Best regards,
    Florian Riedl

  • liblognorm 1.1.3 released

    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