summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2011-03-01 16:01:32 +0100
committerRainer Gerhards <rgerhards@adiscon.com>2011-03-01 16:01:32 +0100
commit75a585a7e26d4d6cf59157cf62584c139af1527c (patch)
treeb7c29c3cb0234f70dcd64259c5b58c64a2311c75 /ChangeLog
parentc130eb20215d5f4ed4fc23c4bf0223b77176617b (diff)
parentbd73f263b310c29d5e0b0dd541403bde44030b86 (diff)
downloadrsyslog-75a585a7e26d4d6cf59157cf62584c139af1527c.tar.gz
rsyslog-75a585a7e26d4d6cf59157cf62584c139af1527c.tar.xz
rsyslog-75a585a7e26d4d6cf59157cf62584c139af1527c.zip
Merge branch 'v5-beta'
Conflicts: ChangeLog
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog16
1 files changed, 16 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 9e76bb11..710cd52c 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -8,6 +8,13 @@ Version 6.1.5 [DEVEL] (rgerhards), 2011-02-??
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=218
- bugfix: memory leak when $RepeatedMsgReduction on was used
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=225
+- bugfix: potential abort condition when $RepeatedMsgReduction set to on
+ as well as potentially in a number of other places where MsgDup() was
+ used. This only happened when the imudp input module was used and it
+ depended on name resolution not yet had taken place. In other words,
+ this was a strange problem that could lead to hard to diagnose
+ instability. So if you experience instability, chances are good that
+ this fix will help.
---------------------------------------------------------------------------
Version 6.1.4 [DEVEL] (rgerhards), 2011-02-18
- bugfix/omhdfs: directive $OMHDFSFileName rendered unusable
@@ -110,6 +117,15 @@ expected that interfaces, even new ones, break during the initial
syslog plain tcp input plugin (NOT supporting TLS!)
[ported from v4]
---------------------------------------------------------------------------
+Version 5.7.7 [V5-BETA] (rgerhards), 2011-03-??
+- bugfix: potential abort condition when $RepeatedMsgReduction set to on
+ as well as potentially in a number of other places where MsgDup() was
+ used. This only happened when the imudp input module was used and it
+ depended on name resolution not yet had taken place. In other words,
+ this was a strange problem that could lead to hard to diagnose
+ instability. So if you experience instability, chances are good that
+ this fix will help.
+---------------------------------------------------------------------------
Version 5.7.6 [V5-BETA] (rgerhards), 2011-02-25
- bugfix: fixed a memory leak and potential abort condition
this could happen if multiple rulesets were used and some output batches