Partially revert prev commit, leave rs->sr_err == SLAPD_ABANDON

[openldap] / servers / slapd / schema / README

diff --git a/servers/slapd/schema/README b/servers/slapd/schema/README
index cd6a1fba2e6cb5a8811e9bbb24c87e42c32b7c44..3eb2303125ff4415aa7d509e2d4f49f61e972504 100644 (file)
--- a/servers/slapd/schema/README
+++ b/servers/slapd/schema/README
@@ -4,33 +4,37 @@ with slapd(8).
 File                    Description
 ----                    -----------
 collective.schema       Collective attributes (experimental)
-corba.schema            Corba Object (RFC 2714)
+corba.schema            Corba Object
 core.schema             OpenLDAP "core"
 cosine.schema           COSINE Pilot
-duaconf.schema          Client Configuration (experimental)
+duaconf.schema          Client Configuration (work in progress)
+dyngroup.schema                        Dynamic Group (experimental)
 inetorgperson.schema    InetOrgPerson
-java.schema             Java Object (RFC 2713)
-microsoft.ext.schema    Microsoft (FYI)
-microsoft.schema        Microsoft (FYI)
-microsoft.std.schema    Microsoft (FYI)
+java.schema             Java Object
 misc.schema             Miscellaneous Schema (experimental)
 nadf.schema             North American Directory Forum (obsolete)
-nis.schema              Network Information Service
+nis.schema              Network Information Service (experimental)
 openldap.schema         OpenLDAP Project (FYI)
-test.schema                            OpenLDAP Software Schema (internal)
-ppolicy.schema          Password Policy Schema (experimental)
-test.schema                            Test Schema
+ppolicy.schema          Password Policy Schema (work in progress)
 
 Additional "generally useful" schema definitions can be submitted
 using the OpenLDAP Issue Tracking System <http://www.openldap.org/its/>.
 Submissions should include a stable reference to a mature, open
 technical specification (e.g., an RFC) for the schema.
 
+The core.ldif and openldap.ldif files are equivalent to their
+corresponding .schema files. They have been provided as examples
+for use with the dynamic configuration backend. These example files
+are not actually necessary since slapd will automatically convert any
+included *.schema files into LDIF when converting a slapd.conf file
+to a configuration database, but they serve as a model of how to
+convert schema files in general.
+
 ---
 
 This notice applies to all files in this directory.
 
-Copyright 1998-2004 The OpenLDAP Foundation, Redwood City, California, USA
+Copyright 1998-2009 The OpenLDAP Foundation, Redwood City, California, USA
 All rights reserved.
 
 Redistribution and use in source and binary forms, with or without