diff options
author | Michael Biebl <biebl@debian.org> | 2013-06-17 17:29:28 +0200 |
---|---|---|
committer | Michael Biebl <biebl@debian.org> | 2013-06-17 17:29:28 +0200 |
commit | c62e2e3b0f562a4ce54f7edcbb76400d90118717 (patch) | |
tree | 8af5c3ee9571e612272f27bef45a701b6c953b13 /ChangeLog | |
parent | a8cc121c4400881b45a9918351a7412053b00816 (diff) | |
download | rsyslog-c62e2e3b0f562a4ce54f7edcbb76400d90118717.tar.gz |
Imported Upstream version 7.4.1upstream/7.4.1
Diffstat (limited to 'ChangeLog')
-rw-r--r-- | ChangeLog | 19 |
1 files changed, 19 insertions, 0 deletions
@@ -1,4 +1,23 @@ --------------------------------------------------------------------------- +Version 7.4.1 [v7.4-stable] 2013-06-17 +- imjournal: add ratelimiting capability + The original imjournal code did not support ratelimiting at all. We + now have our own ratelimiter. This can mitigate against journal + database corruption, when the journal re-sends old data. This is a + current bug in systemd journal, but we won't outrule this to happen + in the future again. So it is better to have a safeguard in place. + By default, we permit 20,000 messages witin 10 minutes. This may + be a bit restrictive, but given the risk potential it seems reasonable. + Users requiring larger traffic flows can always adjust the value. +- bugfix: potential loop in rate limiting + if the message that tells about rate-limiting gets rate-limited itself, + it will potentially create and endless loop +- bugfix: potential segfault in imjournal if journal DB is corrupted +- bugfix: prevent a segfault in imjournal if state file is not defined +- bugfix imzmq3: potential segfault on startup + if no problem happend at startup, everything went fine + Thanks to Hongfei Cheng and Brian Knox for the patch +--------------------------------------------------------------------------- Version 7.4.0 [v7.4-stable] 2013-06-06 This starts a new stable branch based on 7.3.15 plus the following changes: - add --enable-cached-man-pages ./configure option |