Nsslapd-Schemacheck (Schema Checking); Nsslapd-Schemareplace - Netscape DIRECTORY SERVER 6.02 Configuration Manual

Example:
nsslapd-rootpwstoragescheme: SSHA

nsslapd-schemacheck (Schema Checking)

Specifies whether the database schema will be enforced during entry insertion or
modification. When this attribute has a value of on, Directory Server will not check
the schema of existing entries until they are modified. The database schema defines
the type of information allowed in the database. You can extend the default schema
using the
objectclasses
your schema using the Directory Server Console, see Chapter 9, "Extending the
Directory Schema" in the Netscape Directory Server Administrator's Guide.
Schema checking works by default when database modifications
NOTE
are made using an LDAP client, such as
Server Gateway, or when importing a database from LDIF using
ldif2db
manually that your entries conform to the schema. If schema
checking is turned on, the server sends an error message to inform
you of the entries which do not match the schema. Make sure that
the attributes and object classes you create in your LDIF statements
are both spelled correctly and identified in
to create a file in the LDIF format in the schema directory or add the
elements to
Entry DN:
cn=config
Valid Range: on | off
Default Value:
on
Syntax: DirectoryString
Example:
nsslapd-schemacheck: on

nsslapd-schemareplace

Determines whether modify operations that replace attribute values are allowed on
the entry.
cn=schema
Entry DN:
cn=config
and attribute types. For information on how to extend
. If you turn schema checking off, you will have to verify
.
99user.ldif
Chapter 2
Core Server Configuration Attributes Reference
, the Directory
ldapmodify
. You will need
dse.ldif
Core Server Configuration Reference 69