rsyslog 5.9.1 (devel) released
This release offers better systemd integration as well as better support for chrooted environments by supporting better timestamps in these environments. It also contains a number of important bug fixes.
Upgrading to this release is strongly recommended for users of the v5-devel branch.
Remeber that v5-devel receives mostly minor and/or very urgent improvements. The “real” development takes place in v6, which already offers features not found in v5.
ChangeLog:
http://www.rsyslog.com/changelog-for-5-9-1-v5-devel/
Download:
http://www.rsyslog.com/rsyslog-5-9-1-devel/
As always, feedback is appreciated.
Best regards,
Tom Bergfeld
rsyslog 5.9.1 (devel)
Download file name: rsyslog 5.9.1 (devel)
rsyslog 5.9.1 (devel)
md5sum: 99b0f1b9e16f664512ae2f7467eb5c59
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 5.9.1 File size: 2.3 MB
Changelog for 5.9.1 (v5-devel)
Version 5.9.1 [V5-DEVEL] (rgerhards), 2011-06-30
- added support for obtaining timestamp for kernel message from message
If the kernel time-stamps messages, time is now take from that
timestamp instead of the system time when the message was read. This
provides much better accuracy. Thanks to Lennart Poettering for
suggesting this feature and his help during implementation. - added support for obtaining timestamp from system for imuxsock
This permits to read the time a message was submitted to the system
log socket. Most importantly, this is provided in microsecond resolution.
So we are able to obtain high precision timestampis even for messages
that were – as is usual – not formatted with them. This also simplifies
things in regard to local time calculation in chroot environments.
Many thanks to Lennart Poettering for suggesting this feature,
providing some guidance on implementing it and coordinating getting the
necessary support into the Linux kernel. - bugfix: timestamp was incorrectly calculated for timezones with minute
offset
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=271 - bugfix: problems in failover action handling
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=270
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=254 - bugfix: mutex was invalidly left unlocked during action processing
At least one case where this can occur is during thread shutdown, which
may be initiated by lower activity. In most cases, this is quite
unlikely to happen. However, if it does, data structures may be
corrupted which could lead to fatal failure and segfault. I detected
this via a testbench test, not a user report. But I assume that some
users may have had unreproducable aborts that were cause by this bug. - bugfix: memory leak in imtcp & subsystems under some circumstances
This leak is tied to error conditions which lead to incorrect cleanup
of some data structures. [backport from v6] - bugfix/improvement:$WorkDirectory now gracefully handles trailing slashes