From f4dd34d24c22926b76da6f6e1d9f4c471ec2b2da Mon Sep 17 00:00:00 2001
From: rhaggard <rhaggard@localhost>
Date: Fri, 01 Feb 2008 17:30:23 +0000
Subject: [PATCH] commiting configuration XML files after adding info from the old config guide to be incorporated in the new generated config reference
---
opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDVirtualAttributeConfiguration.xml | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDVirtualAttributeConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDVirtualAttributeConfiguration.xml
index b41184c..5950ee0 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDVirtualAttributeConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDVirtualAttributeConfiguration.xml
@@ -33,14 +33,14 @@
<adm:synopsis>
The
<adm:user-friendly-name />
- may be used to ensure that all entries contained in private backends
- will have values for the entryUUID operational attribute.
+ ensures that all entries contained in private backends
+ have values for the entryUUID operational attribute.
</adm:synopsis>
<adm:description>
- The entryUUID values will be generated based on a normalized
- representation of the entry's DN, which should not cause a
- consistency problem because we do not allow modify DN operations to
- be performed in private backends.
+ The entryUUID values are generated based on a normalized
+ representation of the entry's DN, which does not cause a
+ consistency problem because OpenDS does not allow modify DN
+ operations to be performed in private backends.
</adm:description>
<adm:profile name="ldap">
<ldap:object-class>
--
Gitblit v1.10.0