From a728b2c073c7de84e54fc9ca2e14810d9c1d7940 Mon Sep 17 00:00:00 2001 From: Kurt Zeilenga Date: Fri, 19 Jan 2001 18:58:00 +0000 Subject: [PATCH] Minor clean up of unpublished section. --- doc/guide/admin/schema.sdf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guide/admin/schema.sdf b/doc/guide/admin/schema.sdf index 0be8ee628d..5927c5ee4e 100644 --- a/doc/guide/admin/schema.sdf +++ b/doc/guide/admin/schema.sdf @@ -395,10 +395,10 @@ any LDAPv3 server and easily construct directives for use with LDAPv3 servers publish schema elements in special {{subschema}} entries (or subentries). {{slapd}}(8) publishes a single subschema -entry normally named {{EX:cn=Subschema}}. If a server which +entry normally named {{EX:cn=Subschema}}. In a server which supports a single subschema subentry, the DN of the subschema subenty can usually be found by examining the value of the -{{EX:subschemaSubentry}} attribute type in the {{root DSE}} +{{EX:subschemaSubentry}} attribute type in the {{root DSE}}. Other servers may publish multiple subschema entries. These can be located by examining the {{EX:subschemaSubentry}} attribute contained in the entry at the root of each administrative context. -- 2.39.5