summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2012-05-29 11:23:04 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2012-05-29 11:23:04 +0200
commitf4ec11fa779e7348f68ece1b3b50d499a0526ace (patch)
tree3e847b7fa3f9ddbda3266461c10daa4cec68f582 /ChangeLog
parent370bfa988db48ede39e74bcfae0d1909ecb0af66 (diff)
parenta4980cbde24b48c5540435d27d01651d5ca46d03 (diff)
downloadrsyslog-f4ec11fa779e7348f68ece1b3b50d499a0526ace.tar.gz
rsyslog-f4ec11fa779e7348f68ece1b3b50d499a0526ace.tar.xz
rsyslog-f4ec11fa779e7348f68ece1b3b50d499a0526ace.zip
Merge branch 'v5-stable' into v5-beta
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog11
1 files changed, 11 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index fe733c52..3a0d522a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -160,6 +160,17 @@ Version 5.8.12 [V5-stable] 2012-05-??
full delayable sources somewhat smarter and permits, assuming sufficient
timouts, to persist message up to the max queue capacity. Also some nits
in debug instrumentation have been fixed.
+- bugfix/omudpspoof: problems, including abort, happend when run on
+ multiple threads. Root cause is that libnet is not thread-safe.
+ omudpspoof now guards libnet calls with their own mutex.
+- bugfix: if debug message could end up in log file when forking
+ if rsyslog was set to auto-background (thus fork, the default) and debug
+ mode to stdout was enabled, debug messages ended up in the first log file
+ opened. Currently, stdout logging is completely disabled in forking mode
+ (but writing to the debug log file is still possible). This is a change
+ in behaviour, which is under review. If it causes problems to you,
+ please let us know.
+ Thanks to Tomas Heinrich for the patch.
- bugfix/tcpflood: sending small test files did not work correctly
---------------------------------------------------------------------------
Version 5.8.11 [V5-stable] 2012-05-03