diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2010-04-26 15:55:51 +0200 |
---|---|---|
committer | Rainer Gerhards <rgerhards@adiscon.com> | 2010-04-26 15:55:51 +0200 |
commit | ed7f89a49c6f820bc65f87514eb0effafcdeaacc (patch) | |
tree | 86ae5d3cddc18a0efa4330da85fafe8af331a29d /ChangeLog | |
parent | 59497bd057f6ee1bcb626d2ce30bf3eb8ef6ebd0 (diff) | |
parent | 149bab9cd1eb77c0708369d0a56903db90ab9d5f (diff) | |
download | rsyslog-ed7f89a49c6f820bc65f87514eb0effafcdeaacc.tar.gz rsyslog-ed7f89a49c6f820bc65f87514eb0effafcdeaacc.tar.xz rsyslog-ed7f89a49c6f820bc65f87514eb0effafcdeaacc.zip |
Merge branch 'v5-stable'
Diffstat (limited to 'ChangeLog')
-rw-r--r-- | ChangeLog | 19 |
1 files changed, 13 insertions, 6 deletions
@@ -65,12 +65,13 @@ Version 5.5.0 [DEVEL] (rgerhards), 2009-11-18 - doc: improved description of what loadable modules can do --------------------------------------------------------------------------- Version 5.4.2 [v5-stable] (rgerhards), 2010-03-?? -- bugfix(minor): status variable was uninitialized - However, this would have caused harm only if NO parser modules at - all were loaded, which would lead to a defunctional configuration - at all. And, even more important, this is impossible as two parser - modules are built-in and thus can not be "not loaded", so we always - have a minimum of two. +- bugfix(kind of): output plugin retry behaviour could cause engine to loop + The rsyslog engine did not guard itself against output modules that do + not properly convey back the tryResume() behaviour. This then leads to + what looks like an endless loop. I consider this to be a bug of the + engine not only because it should be hardened against plugin misbehaviour, + but also because plugins may not be totally able to avoid this situation + (depending on the type of and processing done by the plugin). - bugfix: testbench failed when not executed in UTC+1 timezone accidently, the time zone information was kept inside some to-be-checked-for responses @@ -78,6 +79,12 @@ Version 5.4.2 [v5-stable] (rgerhards), 2010-03-?? message-induced off-by-one error (potential segfault) (see 4.6.2) The analysis has been completed and a better fix been crafted and integrated. +- bugfix(minor): status variable was uninitialized + However, this would have caused harm only if NO parser modules at + all were loaded, which would lead to a defunctional configuration + at all. And, even more important, this is impossible as two parser + modules are built-in and thus can not be "not loaded", so we always + have a minimum of two. --------------------------------------------------------------------------- Version 5.4.1 [v5-stable] (rgerhards), 2010-03-?? - added new property replacer option "date-rfc3164-buggyday" primarily |