summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorChris St. Pierre <chris.a.st.pierre@gmail.com>2011-12-30 09:53:08 -0500
committerChris St. Pierre <chris.a.st.pierre@gmail.com>2011-12-30 09:53:08 -0500
commitb6654dd316f9cd4f6a6673a89cdd48cc1b38b82a (patch)
treee72cfacc437611f6093f4f4eaccec9cf8e586c8b /doc
parent5fc3effb174ff6e9fbfd05346134ac8861477884 (diff)
downloadbcfg2-b6654dd316f9cd4f6a6673a89cdd48cc1b38b82a.tar.gz
bcfg2-b6654dd316f9cd4f6a6673a89cdd48cc1b38b82a.tar.bz2
bcfg2-b6654dd316f9cd4f6a6673a89cdd48cc1b38b82a.zip
updated docs
Diffstat (limited to 'doc')
-rw-r--r--doc/server/plugins/generators/rules.txt14
1 files changed, 12 insertions, 2 deletions
diff --git a/doc/server/plugins/generators/rules.txt b/doc/server/plugins/generators/rules.txt
index 925ee6419..439bc0281 100644
--- a/doc/server/plugins/generators/rules.txt
+++ b/doc/server/plugins/generators/rules.txt
@@ -354,8 +354,18 @@ how to assign Rules to a host's literal configuration.
Using Regular Expressions in Rules
==================================
-The ``name`` attribute in Rules supports the use of regular
-expressions to match multiple abstract configuration entries.
+If you wish, you can configure the Rules plugin to support regular
+expressions. This entails a small performance and memory usage
+penalty. To do so, create a file, "Rules/rules.conf", and add the
+following text::
+
+ [rules]
+ regex = yes
+
+You will have to restart the Bcfg2 server after making that change.
+
+With regular expressions enabled, you can use a regex in the ``name``
+attribute to match multiple abstract configuration entries.
Regular expressions are anchored at both ends, so ``<Service
name="bcfg2".../>`` will *not* match a Service named ``bcfg2-server``;