From 1c8fe77b78a64d69138b30ec28b430677b197601 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards <rgerhards@adiscon.com>
Date: Wed, 10 Jun 2009 19:03:38 +0200
Subject: added $Ruleset config command

so we now can define multiple rule sets, we just can not use them ;)
That means we have the foundation to bind listeners to different
rule sets.
---
 doc/rsyslog_conf_global.html | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'doc')

diff --git a/doc/rsyslog_conf_global.html b/doc/rsyslog_conf_global.html
index 1e268f4b..e9b1c082 100644
--- a/doc/rsyslog_conf_global.html
+++ b/doc/rsyslog_conf_global.html
@@ -201,6 +201,8 @@ line is that n is large enough to get a good idea which message was repeated but
 large enough for the whole message. (Introduced with 4.1.5). Once set, it affects all following actions.</li>
 <li><a href="rsconf1_repeatedmsgreduction.html">$RepeatedMsgReduction</a></li>
 <li><a href="rsconf1_resetconfigvariables.html">$ResetConfigVariables</a></li>
+<li><b>$Ruleset</b> name - starts a new ruleset. All following actions belong to
+that new rule set.</li>
 <li><b>$OptimizeForUniprocessor</b> [on/<b>off</b>] - turns on optimizatons which lead to better
 performance on uniprocessors. If you run on multicore-machiens, turning this off lessens CPU load. The
 default may change as uniprocessor systems become less common. [available since 4.1.0]</li>
-- 
cgit