rsyslog

ChangeLog for 3.20.5 (v3-stable)

Version 3.20.5 [v3-stable] (rgerhards), 2009-04-02

  • bugfix: potential abort with DA queue after high watermark is reached
    There exists a race condition that can lead to a segfault. Thanks
    go to vbernetr, who performed the analysis and provided patch, which
    I only tweaked a very little bit.

  • fixed bugs in RainerScript:
    • when converting a number and a string to a common type, both were
      actually converted to the other variable’s type.

    • the value of rsCStrConvertToNumber() was miscalculated.
      Thanks to varmojfekoj for the patch
  • fixed a bug in configure.ac which resulted in problems with
    environment detection – thanks to Michael Biebl for the patch

  • fixed a potential segfault problem in gssapi code
    thanks to varmojfekoj for the patch

  • doc enhance: provide standard template for MySQL module and instructions
    on how to modify schema

ChangeLog for 4.1.5 (devel)

Version 4.1.5 [DEVEL] (rgerhards), 2009-03-11

  • bugfix: parser did not correctly parse fields in UDP-received messages
  • added ERE support in filter conditions –
    new comparison operation “ereregex”

  • added new config directive $RepeatedMsgContainsOriginalMsg so that the
    “last message repeated n times” messages, if generated, may
    have an alternate format that contains the message that is being repeated

ChangeLog for 3.20.4 (v3-stable)

Version 3.20.4 [v3-stable] (rgerhards), 2009-02-09

  • bugfix: inconsistent use of mutex/atomic operations could cause segfault
    details are too many, for full analysis see blog post at:
    http://blog.gerhards.net/2009/01/rsyslog-data-race-analysis.html

  • bugfix: invalid ./configure settings for RFC3195
    thanks to Michael Biebl for the patch

  • bugfix: invalid mutex access in msg.c
  • doc bugfix: dist tarball missed 2 files, had one extra file that no
    longer belongs into it. Thanks to Michael Biebl for pointing this out.

ChangeLog for 3.21.10

Version 3.21.10 [BETA] (rgerhards), 2009-02-02

  • bugfix: inconsistent use of mutex/atomic operations could cause segfault
    details are too many, for full analysis see blog post at:
    http://blog.gerhards.net/2009/01/rsyslog-data-race-analysis.html

  • the string “Do Die” was accidently emited upon exit in non-debug mode
    This has now been corrected. Thanks to varmojfekoj for the patch.

  • some legacy options were not correctly processed.
    Thanks to varmojfekoj for the patch.

  • doc bugfix: v3-compatiblity document had typo in config directive
    thanks to Andrej for reporting this

ChangeLog for 4.1.4 (devel)

Version 4.1.4 [DEVEL] (rgerhards), 2009-01-29

  • bugfix: inconsistent use of mutex/atomic operations could cause segfault
    details are too many, for full analysis see blog post at:
    http://blog.gerhards.net/2009/01/rsyslog-data-race-analysis.html

  • bugfix: unitialized mutex was used in msg.c:getPRI
    This was subtle, because getPRI is called as part of the debugging code
    (always executed) in syslogd.c:logmsg.

  • bufgix: $PreserveFQDN was not properly handled for locally emitted
    messages

Changelog for 3.20.3 (v3-stable)

Version 3.20.3 [v3-stable] (rgerhards), 2009-01-19

  • doc bugfix: v3-compatiblity document had typo in config directive
    thanks to Andrej for reporting this

  • fixed a potential segfault condition with $AllowedSender directive
    On HUP, the root pointers were not properly cleaned up. Thanks to
    Michael Biebel, olgoat, and Juha Koho for reporting and analyzing
    the bug.

ChangeLog for 4.1.3 (devel)

Version 4.1.3 [DEVEL] (rgerhards), 2008-12-17

  • added $InputTCPServerAddtlFrameDelimiter config directive, which
    enables to specify an additional, non-standard message delimiter
    for processing plain tcp syslog. This is primarily a fix for the invalid
    framing used in Juniper’s NetScreen products. Credit to forum user
    Arv for suggesting this solution.

  • added $InputTCPServerInputName property, which enables a name to be
    specified that will be available during message processing in the
    inputname property. This is considered useful for logic that treats
    messages differently depending on which input received them.

  • added $PreserveFQDN config file directive
    Enables to use FQDNs in sender names where the legacy default
    would have stripped the domain part.
    Thanks to BlinkMind, Inc. http://www.blinkmind.com for sponsoring this
    development.

  • bugfix: imudp went into an endless loop under some circumstances
    (but could also leave it under some other circumstances…)
    Thanks to David Lang and speedfox for reporting this issue.
Scroll to top