From 742afce7458505be1a82792c9b5728f58456565d Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 13 Jul 2011 12:54:08 +0200 Subject: lexer bug: *.somewhat PRIs not detected regression from last update --- doc/v6compatibility.html | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 doc/v6compatibility.html (limited to 'doc/v6compatibility.html') diff --git a/doc/v6compatibility.html b/doc/v6compatibility.html new file mode 100644 index 00000000..6d60062f --- /dev/null +++ b/doc/v6compatibility.html @@ -0,0 +1,30 @@ + +Compatibility notes for rsyslog v5 + + +

Compatibility Notes for rsyslog v5

Written by Rainer Gerhards +(2009-07-15)

The changes introduced in rsyslog v5 are numerous, but not very intrusive. +This document describes things to keep in mind when moving from v4 to v5. It +does not list enhancements nor does it talk about compatibility concerns introduced +by earlier versions (for this, see their respective compatibility documents). +

HUP processing

The $HUPisRestart directive is supported by some early v5 versions, but has been removed +in 5.1.3 and above. That means that restart-type HUP processing is no longer +available. This processing was redundant and had a lot a drawbacks. +For details, please see the +rsyslog v4 compatibility notes which elaborate +on the reasons and the (few) things you may need to change. +

Queue Worker Thread Shutdown

Previous rsyslog versions had the capability to "run" on zero queue worker +if no work was required. This was done to save a very limited number of resources. However, +it came at the price of great complexity. In v5, we have decided to let a minium of one +worker run all the time. The additional resource consumption is probably not noticable at +all, however, this enabled us to do some important code cleanups, resulting in faster +and more reliable code (complex code is hard to maintain and error-prone). From the +regular user's point of view, this change should be barely noticable. I am including the +note for expert users, who will notice it in rsyslog debug output and other analysis tools. +So it is no error if each queue in non-direct mode now always runs at least one worker +thread. + -- cgit v1.2.3