From 3c1934cf1369a40cb81a03c08b5d3c740740f1fc Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Tue, 10 Sep 2013 13:07:51 +0200 Subject: doc: clarify global/local variables --- ChangeLog | 1 + doc/rainerscript.html | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 76bf4519..3756db73 100644 --- a/ChangeLog +++ b/ChangeLog @@ -14,6 +14,7 @@ Version 7.5.3 [devel] 2013-07-?? that the majority of installations still use legacy config, we considered this behaviour change acceptable and useful. see also: http://blog.gerhards.net/2013/09/imfile-multi-line-messages.html +- add support for global and local variables - bugfix: queue file size was not correctly processed this could lead to using one queue file per message for sizes >2GiB Thanks to Tomas Heinrich for the patch. diff --git a/doc/rainerscript.html b/doc/rainerscript.html index 3eb08eff..aaaced40 100644 --- a/doc/rainerscript.html +++ b/doc/rainerscript.html @@ -68,9 +68,9 @@ local and global variables are also modifieable. represents the root.

Local variables names start with "$.", where the dot denotes the root. Similarly, global variables start with "$/". -

Both JSON properties as well as local variables may contain an arbitrary +

Both JSON properties as well as global/local variables may contain an arbitrary deep path before the final element. The bang character is always used as path -separator, no matter if it is a message property or a local variable. For example +separator, no matter if it is a message property or a global/local variable. For example "$!path1!path2!varname" is a three-level deep message property where as the very similar looking "$.path1!path2!varname" specifies a three-level deep local variable. The similar global variables is named "$/path1!path2!varname". -- cgit v1.2.3