From e6e1ff65bcb577df238c9c24d55909bca6febbb3 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Mon, 9 Jan 2012 14:17:40 +0100 Subject: removing $Begin, $End, $StrictScoping directives v6.4 will provide the same functionality in a far better way. So we do not want to clutter the code. ------------------------- --- doc/Makefile.am | 1 - doc/rsyslog_conf_actions.html | 2 -- doc/scoping.html | 39 --------------------------------------- doc/v6compatibility.html | 3 ++- 4 files changed, 2 insertions(+), 43 deletions(-) delete mode 100644 doc/scoping.html (limited to 'doc') diff --git a/doc/Makefile.am b/doc/Makefile.am index fe96f960..04fda6b3 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -2,7 +2,6 @@ html_files = \ index.html \ bugs.html \ debug.html \ - scoping.html \ features.html \ generic_design.html \ expression.html \ diff --git a/doc/rsyslog_conf_actions.html b/doc/rsyslog_conf_actions.html index 2bcb4146..2e2293ce 100644 --- a/doc/rsyslog_conf_actions.html +++ b/doc/rsyslog_conf_actions.html @@ -8,8 +8,6 @@ message. In general, message content is written to a kind of "logfile". But also other actions might be done, like writing to a database table or forwarding to another host.
-

Please be sure to read about rsyslog config scoping -in combination with this document.
Templates can be used with all actions. If used, the specified template is used to generate the message content (instead of the default diff --git a/doc/scoping.html b/doc/scoping.html deleted file mode 100644 index be80e922..00000000 --- a/doc/scoping.html +++ /dev/null @@ -1,39 +0,0 @@ - -rsyslog configuration scoping - -

rsyslog configuration scoping

-

Starting with version 6.1.0, rsyslog supports -different scopes inside rsyslog.conf. -Earlier versions had only a single, global scope, where each configuration command affected that global -scope. -This resulted in rather complex configurations. Also many users, even the rsyslog authors, were sometimes -not sure what belonged together. So we started an effort to redo the configuration language. -The initial effort, available in 6.1.0, is scoping for actions. Now, an action can be defined -in its own scope and it will always get a fresh environment, not affected by any config -settings outside of that action definition. Similarly, config statements issues within the -scope do not affect the global scope. This is the recommended ways of defining actions. -

However, the previous mode is still supported and any valid pre-v6 config is a valid v6 config -as well. For those interested in more strict scoping, the "$StrictScoping on" directive can -be used to force the use of scopes inside rsyslog.conf. If given, actions and action directives -can not be specified outside of action scopes. -

Nestings of scope is not permitted. Each $Begin must be matched by a $End. This is currently not -enforced in all cases (end of file), but is considered a syntax error which later versions of rsyslog -will most probably detect. -

Note that scoping is in its infancy. Expect changes, and most importantly enhancements. Currently, -scoping is only supported for actions. As a next step, scoping for inputs is planned. Feedback -on the scoping feature is appreciated. -

Scoping Config Statements

- -

[manual index] [rsyslog site]

-

This documentation is part of the rsyslog -project.
-Copyright © 2010 by Rainer Gerhards and -Adiscon. -Released under the GNU GPL version 3 or higher.

- diff --git a/doc/v6compatibility.html b/doc/v6compatibility.html index 3ed5b77d..bc803d2a 100644 --- a/doc/v6compatibility.html +++ b/doc/v6compatibility.html @@ -39,5 +39,6 @@ much coding. However, if the new config language shall be supported, more changes must be made to plugin code. All project-supported plugins have been upgraded, so this compatibility issue is only of interest for you if you have custom plugins or use some user-contributed plugins from the rsyslog project -that are not maintained by the project itself (omoracle is an example). +that are not maintained by the project itself (omoracle is an example). Please +expect some further plugin instablity during the initial v6 releases. -- cgit