summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/Makefile.am5
-rw-r--r--doc/manual.html20
-rw-r--r--doc/v8compatibility.html39
3 files changed, 53 insertions, 11 deletions
diff --git a/doc/Makefile.am b/doc/Makefile.am
index 867a63b7..f7a9efe0 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -121,6 +121,9 @@ html_files = \
v3compatibility.html \
v4compatibility.html \
v5compatibility.html \
+ v6compatibility.html \
+ v7compatibility.html \
+ v8compatibility.html \
im3195.html \
netstream.html \
ns_gtls.html \
@@ -157,8 +160,6 @@ html_files = \
rsconf1_omfileforcechown.html \
rsyslog_queue_pointers.jpeg \
rsyslog_queue_pointers2.jpeg \
- v6compatibility.html \
- v7compatibility.html \
rsyslog_conf_basic_structure.html \
rsyslog_conf_sysklogd_compatibility.html \
imkmsg.html \
diff --git a/doc/manual.html b/doc/manual.html
index 3e3625d9..7ca40491 100644
--- a/doc/manual.html
+++ b/doc/manual.html
@@ -27,16 +27,18 @@ want to lend us a helping hand. </b>It doesn't require a lot of
time - even a single mouse click helps. Learn <a href="how2help.html">how to help the rsyslog project</a>.
Due to popular demand, there is now a <a href="rsyslog_ng_comparison.html">side-by-side comparison
between rsyslog and syslog-ng</a>.</p>
-<p>If you are upgrading from rsyslog v2 or stock sysklogd,
-<a href="v3compatibility.html">be sure to read the rsyslog v3 compatibility notes</a>,
-and if you are upgrading from v3, read the
-<a href="v4compatibility.html">rsyslog v4 compatibility notes</a>,
-if you upgrade from v4, read the
-<a href="v5compatibility.html">rsyslog v5 compatibility notes</a>, and
-if you upgrade from v5, read the
-<a href="v6compatibility.html">rsyslog v6 compatibility notes</a>.
+If you upgrade from v7, read the
+<a href="v8compatibility.html">rsyslog v8 compatibility notes</a>.
if you upgrade from v6, read the
<a href="v7compatibility.html">rsyslog v7 compatibility notes</a>.
+if you upgrade from v5, read the
+<a href="v6compatibility.html">rsyslog v6 compatibility notes</a>.
+if you upgrade from v4, read the
+<a href="v5compatibility.html">rsyslog v5 compatibility notes</a>.
+if you upgrade from v3, read the
+<a href="v4compatibility.html">rsyslog v4 compatibility notes</a>.
+<p>If you are upgrading from rsyslog v2 or stock sysklogd,
+<a href="v3compatibility.html">be sure to read the rsyslog v3 compatibility notes</a>,
<p>Rsyslog will work even
if you do not read the doc, but doing so will definitely improve your experience.</p>
<p><b>Follow the links below for the</b></p>
@@ -44,7 +46,7 @@ if you do not read the doc, but doing so will definitely improve your experience
<li><a href="troubleshoot.html">troubleshooting rsyslog problems</a></li>
<li><a href="rsyslog_conf.html">configuration file format (rsyslog.conf)</a></li>
<li><a href="http://www.rsyslog.com/tool-regex">a regular expression checker/generator tool for rsyslog</a></li>
-<li> <a href="property_replacer.html">property replacer, an important core component</a></li>
+<li><a href="property_replacer.html">property replacer, an important core component</a></li>
<li><a href="bugs.html">rsyslog bug list</a></li>
<li><a href="messageparser.html">understanding rsyslog message parsers</a></li>
<li><a href="generic_design.html">backgrounder on generic syslog application design</a></li>
diff --git a/doc/v8compatibility.html b/doc/v8compatibility.html
new file mode 100644
index 00000000..aedc755f
--- /dev/null
+++ b/doc/v8compatibility.html
@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>Compatibility notes for rsyslog v8</title>
+</head>
+<body>
+<h1>Compatibility Notes for rsyslog v8</h1>
+This document describes things to keep in mind when moving from v7 to v8. It
+does not list enhancements nor does it talk about compatibility concerns introduced
+by earlier versions (for this, see their respective compatibility documents). Its focus
+is primarily on what you need to know if you used v7 and want to use v8 without hassle.
+<p>Version 8 offers a completely rewritten core rsyslog engine. This resulted in
+a number of changes that are visible to users and (plugin) developers.
+Most importantly, pre-v8 plugins <b>do not longer work</b> and need to
+be updated to support the new calling interfaces. If you developed a plugin,
+be sure to review the developer section below.
+</p>
+<h2>What Developers need to Know</h2>
+<h3>output plugin interface</h3>
+<p>To support the new core engine, the output interface has been considerably
+changed. It is suggested to review some of the project-provided plugins for
+full details. In this doc, we describe the most important changes from a high
+level perspective.
+<p><b>RS_RET_SUSPENDED is no longer supported when creating an action instance</b>
+<p>This means a plugin must not try to establish any connections or the like
+before any of its processing entry points (like beginTransaction or doAction)
+is called. This was generally also the case von v7, but was not enforced in
+all cases. In v8, creating action creation fails if anything but RS_RET_OK
+is returned.
+
+
+<a href="http://www.rsyslog.com/g/BSD">rsyslog BSD blocks info</a>
+page for more information and how to upgrade your config.
+<p>[<a href="manual.html">manual index</a>] [<a href="http://www.rsyslog.com/">rsyslog site</a>]</p>
+
+<p><font size="2">This documentation is part of the
+<a href="http://www.rsyslog.com/">rsyslog</a> project.<br>
+Copyright &copy; 2013 by <a href="http://www.gerhards.net/rainer">Rainer Gerhards</a> and
+<a href="http://www.adiscon.com/">Adiscon</a>. Released under the GNU GPL
+version 2 or higher.</font></p>
+</body></html>