From 8546cd810e8ef3f58ae010759de2b1f5f05bc7b3 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards <rgerhards@adiscon.com>
Date: Wed, 30 Oct 2013 17:47:13 +0100
Subject: doc: clarify rulesets and main queues

---
 doc/multi_ruleset.html | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/multi_ruleset.html b/doc/multi_ruleset.html
index 14a761c5..1be2c81e 100644
--- a/doc/multi_ruleset.html
+++ b/doc/multi_ruleset.html
@@ -89,6 +89,15 @@ modify the ruleset to which the next input is bound but rather provides a system
 default rule set for those inputs that did not explicitly bind to one. As such, the directive
 can not be used as a work-around to bind inputs to non-default rulesets that do not support
 ruleset binding.
+
+<h2>Rulesets and Main Queues</h2>
+By default, rulesets do not have their own queue. It must be activated via
+the $RulesetCreateMainQueue directive, or if using rainerscript format, by
+specifying queue parameters on the ruleset directive, e.g.
+ruleset(name="whatever" queue.type="fixedArray" queue. ...)
+See <a href="http://www.rsyslog.com/doc/queue_parameters.html">http://www.rsyslog.com/doc/queue_parameters.html</a>
+for more details. 
+
 <h2>Examples</h2>
 <h3>Split local and remote logging</h3>
 <p>Let's say you have a pretty standard system that logs its local messages to the usual
-- 
cgit v1.2.3