location of an entry by changing the DN of the entry to conform to the views
hierarchy. This is by design—many applications would not function if the true
location of an entry is disguised. For example, those applications that rely on
the DN to identify a unique entry. This upward navigation by deconstructing a
DN is an unusual technique for a client application, but nonetheless, those
clients that do this may not function as intended.
•
Applications that use the
how many entries exist beneath a node. For views nodes, this is currently a
count of only those entries that exist in the real search space, ignoring the
virtual search space. Applications may not evaluate the view with a search as a
result of this.
Other Directory Tree Resources
Take a look at the following links for more information about designing your
directory tree:
•
RFC 2247: Using Domains in LDAP/X.500 Distinguished Names
http://www.ietf.org/rfc/rfc2247.txt
•
RFC 2253: LDAPv3, UTF-8 String Representation of Distinguished Names
http://www.ietf.org/rfc/rfc2253.txt
operational attribute to determine
numSubordinates
Chapter 4
Other Directory Tree Resources
Designing the Directory Tree
85
Need help?
Do you have a question about the NETSCAPE DIRECTORY SERVER 6.2 - DEPLOYMENT and is the answer not in the manual?
Questions and answers