From 082737dec693fbb531ca9dad3ab9b638baaa3327 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards <rgerhards@adiscon.com>
Date: Mon, 28 Jan 2008 10:47:34 +0000
Subject: added some doc on how to handle massive amounts of database inserts
 with     rsyslog

---
 doc/rsyslog_high_database_rate.html | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/doc/rsyslog_high_database_rate.html b/doc/rsyslog_high_database_rate.html
index 213050e6..41eb6b6a 100644
--- a/doc/rsyslog_high_database_rate.html
+++ b/doc/rsyslog_high_database_rate.html
@@ -72,15 +72,19 @@ restarts, so even a reboot of the system will not cause any message loss.</p>
 disk queue and then configure your action. There is nothing else to do. With the 
 following simple config file, you log anything you receive to a MySQL database 
 and have buffering applied automatically.</p>
-<textarea rows="11" cols="80">
-$ModLoad ommysql.so # load the output driver (use ompgsql.so for PostgreSQL)
+<textarea rows="11" cols="80">$ModLoad ommysql.so # load the output driver (use ompgsql.so for PostgreSQL)
 $ModLoad imudp.so # network reception
 $ModLoad imuxsock.so # local message reception
-$MainMessage
+
+$WorkDirectory /home/rger/proj/rsyslog/spool # default location for work (spool) files
+$MainMsgQueueFileName mainq # set file name, also enables disk mode
 
 *.* :ommysql:
 </textarea>
-<p>&nbsp;</p>
+<p>Note that you can modify a lot of queue performance parameters, but the above
+config will get you going with default values. If you consider using this on a real
+busy server, it is strongly recommended to invest some time in setting the tuning
+parameters to appropriate values.</p>
 
 <h3>Feedback requested</h3>
 
@@ -125,4 +129,4 @@ http://www.gnu.org/copyleft/fdl.html</a>.</p>
 
 </body>
 
-</html>
\ No newline at end of file
+</html>
-- 
cgit v1.2.3