rsyslog 6.3.2 (devel) released
This release offers better support for systemd and better timestamps for local log messages as well as an important syntax enhancement for omusrmsg. It also contains some bug fixes.
It is a recommended update for all v6-devel users.
ChangeLog:
http://www.rsyslog.com/changelog-for-6-3-2-v6-devel/
Download:
http://www.rsyslog.com/rsyslog-6-3-2-devel/
As always, feedback is appreciated.
Best regards,
Tom Bergfeld
rsyslog 6.3.2 (devel)
Download file name: rsyslog 6.3.2 (devel)
rsyslog 6.3.2 (devel)
md5sum: bdbe653301fa0250b365dafd12617d66
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 6.3.2 File size: 2.3 MB
Changelog for 6.3.2 (v6-devel)
Version 6.3.2 [DEVEL] (rgerhards), 2011-07-06
- added support for the “:omusrmsg:” syntax in configuring user messages
- systemd support: set stdout/stderr to null – thx to Lennart for the patch
- 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: memory leak in imtcp & subsystems under some circumstances
This leak is tied to error conditions which lead to incorrect cleanup
of some data structures.