Release bumped to "gts4".

[tac_plus.git] / users_guide

diff --git a/users_guide b/users_guide
index 13204b7..c1a8cfd 100644 (file)
--- a/users_guide
+++ b/users_guide
@@ -404,7 +404,11 @@ group = city_X_NASes {
 As you can see, "enlist" doesn't require the existence of the given entity as
 it would loose its primary purpose. If the entity doesn't exist it will be
 automatically created (as empty one) - this doesn't apply to "member"! Any
-argument to "member" MUST exist.
+argument to "member" MUST already exist. "enlist" is provided to save you from
+writing a lot of empty definition lines like:
+
+host =  first.NAS.X.city {
+}
 
 All forward references are not a problem, you can still make membership or
 enlistment on the top of the file with the entity which will be defined on the
@@ -1182,12 +1186,16 @@ user = fred {
        }
     }
 }
-host = machine.A.company {
-}
 
    You can see the (nested) command "when" can limit the scope of existence of
-   its contents. Unfortunately you cannot use "when" to limit any items, just
-   a few are possible:
+   its contents. Definition of "host machine.A.company" with empty block (no
+   attributes) isn't needed as "when" line will automatically create hosts not
+   defined elsewhere, in the same style as "enlist" keyword creates them. Any
+   "user"s or "group"s referenced by "when" MUST be defined, such entities are
+   never created automatically!
+   
+   Unfortunately you cannot use "when" to limit any items, just a few of them
+   are possible:
 
 member
 enlist