Table
Configuration file name | Purpose |
Schema used by Netscape Messaging Server to define mail users and mail groups. | |
|
|
Schema for servers' value item attributes. | |
|
|
Schema for Netscape Web Server. | |
|
|
Reserved for future use. | |
|
|
99user.ldif | |
| contains the attributes and object classes from the suppliers. |
|
|
The dse.ldif file contains all configuration information including
When the server generates the dse.ldif file, it lists the entries in hierarchical order in the order that the entries appear in the directory under cn=config, which is usually the same order in which an LDAP search of subtree scope for base cn=config returns the entries.
dse.ldif also contains the cn=monitor entry, which is mostly
NOTE:
The dse.ldif file does not contain every attribute in cn=config. If the attribute has not been set by the administrator and has a default value, the server will not write it to dse.ldif. To see every attribute in cn=config, use the ldapsearch command.
2.1.2.1 Configuration attributes
Within a configuration entry, each attribute is represented as an attribute name. The value of the attribute corresponds to the attribute's configuration.
The following code sample is an example of part of the dse.ldif file for a Directory Server. The example shows, among other things, that schema checking has been enabled; this is represented by the attribute
dn: cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsslapdConfig
...
2.1.2.2 Configuration of
The configuration for each part of Directory Server
dn: cn=Telephone Syntax,cn=plugins,cn=config
objectclass: top
2.1 Overview of the Directory Server configuration | 19 |