stable

Version 4.6.1 [v4-stable] (rgerhards), 2010-03-04

• re-enabled old pipe output (using new module ompipe, built-in) after some problems with pipes (and especially in regard to xconsole) were discovered.
  Thanks to Michael Biebl for reporting the issues.

• bugfix: potential problems with large file support could cause segfault … and other weird problems. This seemed to affect 32bit-platforms only, but I can not totally outrule there were issues on other platforms as well. The previous code could cause system data types to be defined inconsistently, and that could lead to various troubles.
  Special thanks go to the Mandriva team for identifying an initial problem, help discussing it and ultimately a fix they contributed.

• bugfix: fixed problem that caused compilation on FreeBSD 9.0 to fail.
  bugtracker: http://bugzilla.adiscon.com/show_bug.cgi?id=181
  Thanks to Christiano for reporting.

• bugfix: potential segfault in omfile when a dynafile open failed
  In that case, a partial cache entry was written, and some internal pointers (iCurrElt) not correctly updated. In the next iteration, that could lead to a segfault, especially if iCurrElt then points to the then-partial record. Not very likely, but could happen in practice.

• bugfix (theoretical): potential segfault in omfile under low memory condition. This is only a theoretical bug, because it would only happen when strdup() fails to allocate memory – which is highly unlikely and will probably lead to all other sorts of errors.
• bugfix: comment char (‘#’) in literal terminated script parsing and thus could not be used. bugtracker: http://bugzilla.adiscon.com/show_bug.cgi?id=119
  [merged in from v3.22.2]

Version 5.2.0 [v5-stable] (rgerhards), 2009-11-02
This is a re-release of version 5.1.6 as stable after we did not get any bug reports during the whole beta phase. Still, this first v5-stable may not be as stable as one hopes for, I am not sure if we did not get bug reports just because nobody tried it. Anyhow, we need to go forward and so we have the initial v5-stable.

Version 4.4.2 [v4-stable] (rgerhards), 2009-10-09

• bugfix: invalid handling of zero-sized messages, could lead to mis-addressing and potential memory corruption/segfault
• bugfix: zero-sized UDP messages are no longer processed until now, they were forwarded to processing, but this makes no sense. Also, it looks like the system seems to provide a zero return code on a UDP recvfrom() from time to time for some internal reasons. These “receives” are now silently ignored.
• bugfix: random data could be appended to message, possibly causing segfaults
• bugfix: reverse lookup reduction logic in imudp do DNS queries too often
  A comparison was done between the current and the former source address. However, this was done on the full sockaddr_storage structure and not on the host address only. This has now been changed for IPv4 and IPv6. The end result of this bug could be a higher UDP message loss rate than necessary (note that UDP message loss can not totally be avoided due to the UDP spec)

Version 4.4.1 [v4-stable] (rgerhards), 2009-09-02

• features requiring Java are automatically disabled if Java is not present (thanks to Michael Biebl for his help!)
• bugfix: invalid double-quoted PRI, among others in outgoing messages. This causes grief with all receivers. Bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=147
• bugfix: Java testing tools were required, even if testbench was disabled. This resulted in build errors if no Java was present on the build system, even though none of the selected option actually required Java. (I forgot to backport a similar fix to newer releases).
• bugfix (backport): omfwd segfault. Note that the orginal (higher version) patch states this happens only when debugging mode is turned on. That statement is wrong: if debug mode is turned off, the message is not being emitted, but the division
  by zero in the actual parameters still happens.

Version 4.4.0 [v4-stable] (rgerhards), 2009-08-21

• bugfix: stderr/stdout were not closed to be able to emit error messages, but this caused ssh sessions to hang. Now we close them after the initial initialization. See forum thread: http://kb.monitorware.com/controlling-terminal-issues-t9875.html
• bugfix: sending syslog messages with zip compression did not work
  

Version 3.22.1 [v3-stable] (rgerhards), 2009-07-02

• bugfix: invalid error message issued if $inlcudeConfig was on an empty set of files (e.g. *.conf, where none such files existed) thanks to Michael Biebl for reporting this bug
• bugfix: when run in foreground (but not in debug mode), a debug message (“DoDie called”) was emitted at shutdown. Removed. thanks to Michael Biebl for reporting this bug
• bugfix: some garbagge was emitted to stderr on shutdown. This garbage consisted of file names, which were written during startup (key point: not a pointer error) thanks to Michael Biebl for reporting this bug
• bugfix: startup and shutdown message were emitted to stdout thanks to Michael Biebl for reporting this bug
• bugfix: error messages were not emitted to stderr in forked mode
  (stderr and stdo are now kept open across forks)

• bugfix: internal messages were emitted to whatever file had fd2 when rsyslogd ran in forked mode (as usual!) Thanks to varmojfekoj for the patch
• small enhancement: config validation run now exits with code 1 if an error is detected. This change is considered important but small enough to apply it directly to the stable version. [But it is a border case, the change requires more code than I had hoped. Thus I have NOT tried to actually catch all cases, this is left for the current devel releases, if necessary]
• bugfix: light and full delay watermarks had invalid values, badly affecting performance for delayable inputs
• bugfix: potential segfault issue when multiple $UDPServerRun directives are specified. Thanks to Michael Biebl for helping to debug this one.
• relaxed GnuTLS version requirement to 1.4.0 after confirmation from the field that this version is sufficient
• bugfix: parser did not properly handle empty structured data
• bugfix: invalid mutex release in msg.c (detected under thread debugger, seems not to have any impact on actual deployments)