Re-factor the directive message change

- results in much more compact code
- Document change in the config basics doc

Signed-off-by: Tom Eastep <teastep@shorewall.net>

Shorewall/Actions/action.GlusterFS

@@ -13,9 +13,9 @@
 DEFAULTS 2,0
 
 ?if @1 !~ /^\d+/ || ! @1 || @1 > 1024
-    ?error Invalid value for Bricks (@1)
+    ?error Invalid value (@1) for the GlusterFS Bricks argument
 ?elsif @2 !~ /^[01]$/
-    ?error Invalid value for IB (@2)
+    ?error Invalid value (@2) for the GlusterFS IB argument
 ?endif
 
 #ACTION		SOURCE		DEST		PROTO	DPORT

docs/configuration_file_basics.xml

@@ -2275,6 +2275,18 @@ SSH(ACCEPT)    net:$MYIP      $FW
     <command>restart</command>, <command>reload</command>,
     <command>refresh</command>, or one of the <command>safe</command>-*
     commands.</para>
+
+    <para>See the VERBOSE_MESSAGES option in <ulink
+    url="manpages/shorewall.conf.html">shorewall.conf(5)</ulink> for
+    additional information.</para>
+
+    <para>In Shorewall 5.1.4, the behavior of ?ERROR, ?WARNING and ?INFO was
+    changed when they appear in an action file. Rather than reporting the
+    action filename and line number, the generated message reports where the
+    action was invoked. For example, the GlusterFS message above was changed
+    to:</para>
+
+    <programlisting>   ERROR: Invalid value (2000) for the GlusterFS Bricks argument /etc/shorewall/rules (line 45)</programlisting>
   </section>
 
   <section id="Embedded">