From 37737e52ffa8025dc5206dfeb6e6ba46e75f25fe Mon Sep 17 00:00:00 2001
From: rhaggard <rhaggard@localhost>
Date: Wed, 06 Feb 2008 18:09:50 +0000
Subject: [PATCH] Commiting configuration XML files after adding info from the old config guide to be incorporated in the new generated config reference
---
opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml | 17 ++++++++---------
1 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml b/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
index 0199388..6632767 100644
--- a/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
+++ b/opendj-sdk/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
@@ -23,7 +23,7 @@
! CDDL HEADER END
!
!
- ! Portions Copyright 2007 Sun Microsystems, Inc.
+ ! Portions Copyright 2007-2008 Sun Microsystems, Inc.
! -->
<adm:managed-object name="replication-domain"
plural-name="replication-domains"
@@ -74,8 +74,7 @@
<adm:property name="server-id" mandatory="true" read-only="true">
<adm:synopsis>
Specifies a unique identifier for the Directory Server within the
- <adm:user-friendly-name />
- .
+ <adm:user-friendly-name />.
</adm:synopsis>
<adm:description>
Each Directory Server within the same
@@ -134,10 +133,10 @@
use when communicating with Replication Servers.
</adm:synopsis>
<adm:description>
- The Directory Server will expect a regular heart-beat coming from
+ The Directory Server expects a regular heart-beat coming from
the Replication Server within the specified interval. If a
heartbeat is not received within the interval, the Directory
- Server will close its connection and connect to another
+ Server closes its connection and connects to another
Replication Server.
</adm:description>
<adm:default-behavior>
@@ -172,10 +171,10 @@
<adm:synopsis>
Indicates that updates should be accepted even though it is
not possible to send them to any Replication Server. Best
- effort will be made to re-send those updates to a
+ effort is made to re-send those updates to a
Replication Servers when one of them is available, however
- those changes will be at risk because they will only be
- available from the historical information. This mode may
+ those changes are at risk because they are only
+ available from the historical information. This mode can
also introduce high replication latency.
</adm:synopsis>
</adm:value>
@@ -183,7 +182,7 @@
<adm:synopsis>
Indicates that all updates attempted on this
<adm:user-friendly-name />
- will be rejected when no Replication Server is available.
+ are rejected when no Replication Server is available.
</adm:synopsis>
</adm:value>
</adm:enumeration>
--
Gitblit v1.10.0