summaryrefslogtreecommitdiffstats
path: root/doc/omruleset.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/omruleset.html')
-rw-r--r--doc/omruleset.html19
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/omruleset.html b/doc/omruleset.html
index 41d6ccfc..3911929d 100644
--- a/doc/omruleset.html
+++ b/doc/omruleset.html
@@ -10,6 +10,20 @@
<p><b>Module Name:&nbsp;&nbsp;&nbsp; omruleset</b></p>
<p><b>Author: </b>Rainer Gerhards &lt;rgerhards@adiscon.com&gt;</p>
<p><b>Available Since</b>: 5.3.4</p>
+<p><b><font color="red">Deprecated in</font></b>: 7.2.0+</p>
+<p><b>Deprecation note</b></p>
+<p><font color="red">This module exists only for backwards-compatibility
+reasons.</font>
+<b>Do no longer use it in new configurations.</b> It has been
+replaced by the much more efficient
+<a href="rainerscript_call.html">"call" RainerScript statement</a>. The
+"call" statement supports everything omruleset does, but in an easier
+to use way.
+<br>
+<br>
+<br>
+<br>
+<br>
<p><b>Description</b>:</p>
<p>This is a very special &quot;output&quot; module. It permits to pass a message object
to another rule set. While this is a very simple action, it enables very
@@ -122,6 +136,11 @@ $ActionOmrulesetRulesetName nested
# of course, we can have "regular" actions alongside :omrulset: actions
*.* /path/to/general-message-file.log
</textarea>
+<p><b>See Also</b>
+<ul>
+<li><a href="http://www.rsyslog.com/rulesets-and-rsyslog-7-2/">Calling rulesets since rsyslog 7.2</a></li>
+</ul>
+</p>
<p><b>Caveats/Known Bugs:</b>
<p>The current configuration file language is not really adequate for a complex construct
like omruleset. Unfortunately, more important work is currently preventing me from redoing the