From ca5a70aa6f8c785f525d5806f2fbf6922881e843 Mon Sep 17 00:00:00 2001 From: Tom Eastep Date: Sat, 2 Feb 2013 11:08:29 -0800 Subject: [PATCH] Clarify the forms allowed in a ?SET directive. Signed-off-by: Tom Eastep --- docs/configuration_file_basics.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/configuration_file_basics.xml b/docs/configuration_file_basics.xml index ed43c0e73..d5aae3e82 100644 --- a/docs/configuration_file_basics.xml +++ b/docs/configuration_file_basics.xml @@ -1484,7 +1484,8 @@ SHELL cat /etc/shorewall/rules.d/*.rules 2> /dev/null || true The variable can be specified either with or without a leading '$' to allow using both Perl and - Shell variable representation. + Shell variable representation. The ${...} form (e.g. ${foo}) is not + allowed. The value is a Perl-compatible expression. @@ -1517,6 +1518,11 @@ SHELL cat /etc/shorewall/rules.d/*.rules 2> /dev/null || trueAction variables are read-only and cannot be ?SET (although you can change their values using embedded Perl). + + Beginning with Shorewall 4.5.13, Shorewall Variables may be set. When + setting a Shorewall Variable, the variable must + include the leading '@' and the @{...} form is not allowed.
@@ -1861,7 +1867,7 @@ SHELL cat /etc/shorewall/rules.d/*.rules 2> /dev/null || trueBeginning with Shorewall 4.5.13, the values of @chain and @disposition are used to generated the --log-prefix in logging rules. When either is empty, the historical value is used to generate the - --log-prefix. + --log-prefix.