summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2007-08-14 08:33:11 +0000
committerRainer Gerhards <rgerhards@adiscon.com>2007-08-14 08:33:11 +0000
commitda3b996acc97244dc1f96a47b81a06d16791efce (patch)
tree1c72336959164e28e3c97f03c5f65d3b1d17ee18
parent87445422bf96c457b40eaa2dca212c3b416d34ba (diff)
downloadrsyslog-da3b996acc97244dc1f96a47b81a06d16791efce.tar.gz
rsyslog-da3b996acc97244dc1f96a47b81a06d16791efce.tar.xz
rsyslog-da3b996acc97244dc1f96a47b81a06d16791efce.zip
reflect arrival of dynamically loadable plug-ins (namely MySQL)
-rw-r--r--doc/rsconf1_modload.html7
-rw-r--r--doc/rsyslog_conf.html10
2 files changed, 9 insertions, 8 deletions
diff --git a/doc/rsconf1_modload.html b/doc/rsconf1_modload.html
index 7108a21b..48bb8ab0 100644
--- a/doc/rsconf1_modload.html
+++ b/doc/rsconf1_modload.html
@@ -7,9 +7,12 @@
<p><b>Type:</b> global configuration directive</p>
<p><b>Default:</b> </p>
<p><b>Description:</b></p>
-<p>This currently is a dummy directive. It will support the loading of plug-ins in future releases of rsyslog supporting plug-ins. Currently, only "MySQL" is supported as parameter. This activates MySQL support (if rsyslog is compiled with MySQL functionality).</p>
+<p>Dynamically loads a plug-in into rsyslog's address space and activates it.
+The plug-in must obey the rsyslog module API. Currently, only MySQL is available
+as a plugin, but others may create their own. A plug-in must be loaded BEFORE
+any configuration file lines that reference it.</p>
<p><b>Sample:</b></p>
-<p><code><b>$ModLoad MySQL</b></code></p>
+<p><code><b>$ModLoad MySQL&nbsp; # load MySQL functionality</b></code></p>
<p>[<a href="rsyslog_conf.html">rsyslog.conf overview</a>] [<a href="manual.html">manual
index</a>] [<a href="http://www.rsyslog.com/">rsyslog site</a>]</p>
diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html
index dcbf5dad..2089b87a 100644
--- a/doc/rsyslog_conf.html
+++ b/doc/rsyslog_conf.html
@@ -530,7 +530,7 @@ something strange is happening with the system. To specify this wall(1)-feature
use an asterisk (&quot;*'').</p>
<h3>Database Table</h3>
<p>This allows logging of the message to a database table. Currently, only MySQL
-databases are supported. By default, a MonitorWare-compatible schema is required
+databases are supported. By default, a <a href="http://www.monitorware.com/">MonitorWare</a>-compatible schema is required
for this to work. You can create that schema with the createDB.SQL file that
came with the rsyslog package. You can also<br>
use any other schema of your liking - you just need to define a proper template
@@ -544,14 +544,12 @@ template is to be used, a semicolon followed by the template name can follow
the connect information. This is as follows:<br>
<br>
&gt;dbhost,dbname,dbuser,dbpassword;dbtemplate</p>
-<p><b>Important: to use the database functionality, MySQL must be enabled in the
-config file</b> BEFORE the first database table action is used. This is done by
+<p><b>Important: to use the database functionality, the MySQL output module must be
+loaded in the config file</b> BEFORE the first database table action is used. This is done by
placing the</p>
<p><code><b>$ModLoad MySQL</b></code></p>
<p>directive some place above the first use of the database write (we recommend
-doing at the the begining of the config file). <b>Please note that rsyslog must
-also have been built with MySQL support</b> (many packages do not do this by
-default).</p>
+doing at the the beginning of the config file).</p>
<h3>Discard</h3>
<p>If the discard action is carried out, the received message is immediately
discarded. No further processing of it occurs. Discard has primarily been added