From: Howard Chu <hyc@openldap.org>
Date: Sun, 14 Aug 2005 08:48:57 +0000 (+0000)
Subject: ITS#3936 fix wording, add clarification
X-Git-Tag: OPENLDAP_REL_ENG_2_2_MP~706
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=19b8e9e1ce9cb400d929f5f610549bef7bc9090b;p=openldap

ITS#3936 fix wording, add clarification
---

diff --git a/doc/man/man5/slapo-unique.5 b/doc/man/man5/slapo-unique.5
index ae30ff1a20..4ad9dc9162 100644
--- a/doc/man/man5/slapo-unique.5
+++ b/doc/man/man5/slapo-unique.5
@@ -58,7 +58,7 @@ attributes, as these will generally not be unique, nor are they operational
 attributes.
 .TP
 .B unique_attributes <attribute...>
-Specify one or more attributes which for which uniqueness will be enforced.
+Specify one or more attributes for which uniqueness will be enforced.
 If not specified, all attributes which are not operational (eg, system
 attributes such as
 .B entryUUID )
@@ -79,7 +79,15 @@ on the
 list, and included in the
 .B unique_attributes
 list, in that order. This makes it possible to create interesting and
-unusable configurations.
+unusable configurations. Usually only one of
+.B unique_ignore
+or
+.B unique_attributes
+should be configured; use
+.B unique_ignore
+if the majority of attributes should be unique, and use
+.B unique_attributes
+if only a small set of attributes should be unique.
 .LP
 Typical attributes for the
 .B unique_ignore