summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2009-10-26 10:09:04 +0100
committerRainer Gerhards <rgerhards@adiscon.com>2009-10-26 10:09:04 +0100
commit6be07a8f8a3b9b7baf77e42639473e9b1a990e29 (patch)
treedade763f274a4a035cd6fed684c7eeb17599e37e /ChangeLog
parenteb5cb72ec4cb4ac5d7f13855ac4dac9b6927078c (diff)
downloadrsyslog-6be07a8f8a3b9b7baf77e42639473e9b1a990e29.tar.gz
rsyslog-6be07a8f8a3b9b7baf77e42639473e9b1a990e29.tar.xz
rsyslog-6be07a8f8a3b9b7baf77e42639473e9b1a990e29.zip
bugfix: potential abort if inputname property was not set
primarily a problem of imdiag. Also added some fix for a potential situation during cancel processing. That one is not considered vital and may later be removed again.
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog2
1 files changed, 2 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index d2d65838..ca873ef5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -5,6 +5,8 @@ Version 5.3.3 [DEVEL] (rgerhards), 2009-10-??
value for malloced memory (optional, only if requested by configure
option). This helps to track down some otherwise undetected issues
within the testbench.
+- bugfix: potential abort if inputname property was not set
+ primarily a problem of imdiag
- bugfix: message processing states were not set correctly in all cases
however, this had no negative effect, as the message processing state
was not evaluated when a batch was deleted, and that was the only case