summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2012-06-01 16:51:03 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2012-06-01 16:51:03 +0200
commit4a37e5daba6ede7c8c486c14a3403d495d21c697 (patch)
treeaddd96ca550f31b9f5f0d17b558f91a79c94a881 /ChangeLog
parent00ce927aa99e40cd8a917963f7c7d7ea6785f118 (diff)
parentd6602c1a6cfd48ff1f5b7656eb429d60ce927ebc (diff)
downloadrsyslog-4a37e5daba6ede7c8c486c14a3403d495d21c697.tar.gz
rsyslog-4a37e5daba6ede7c8c486c14a3403d495d21c697.tar.xz
rsyslog-4a37e5daba6ede7c8c486c14a3403d495d21c697.zip
Merge branch 'v5-beta' into beta
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog14
1 files changed, 14 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 985287da..2e9b8348 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -454,6 +454,13 @@ expected that interfaces, even new ones, break during the initial
[ported from v4]
---------------------------------------------------------------------------
Version 5.9.8 [V5-BETA], 2012-05-??
+- bugfix: delayble source could block action queue, even if there was
+ a disk queue associated with it. The root cause of this problem was
+ that it makes no sense to delay messages once they arrive in the
+ action queue - the "input" that is being held in that case is the main
+ queue worker, what makes no sense.
+ Thanks to Marcin for alerting us on this problem and providing
+ instructions to reproduce it.
- bugfix: disk queue was not persisted on shutdown, regression of fix to
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and
@@ -611,6 +618,13 @@ Version 5.9.0 [V5-DEVEL] (rgerhards), 2011-06-08
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=236
---------------------------------------------------------------------------
Version 5.8.12 [V5-stable] 2012-05-??
+- bugfix: delayble source could block action queue, even if there was
+ a disk queue associated with it. The root cause of this problem was
+ that it makes no sense to delay messages once they arrive in the
+ action queue - the "input" that is being held in that case is the main
+ queue worker, what makes no sense.
+ Thanks to Marcin for alerting us on this problem and providing
+ instructions to reproduce it.
- bugfix: disk queue was not persisted on shutdown, regression of fix to
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and