mirror/openldap
2
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-01-06 10:46:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

HEADS-UP: now the list of URIs is better set by using separate arguments

Browse Source
This commit is contained in:
Pierangelo Masarati 2007-09-13 18:40:19 +00:00
parent d6baaffbec
commit 27003dccd5
1 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/man/man5/slapd-meta.5
View File

@ -196,16 +196,15 @@ for a shared one; otherwise, wait until the shared connection is available.
Target specification starts with a "uri" directive: Target specification starts with a "uri" directive:
.TP .TP
.B uri <protocol>://[<host>[:<port>]]/<naming context> .B uri <protocol>://[<host>]/<naming context> [...]
The "server" directive that was allowed in the LDAP backend (although
deprecated) has been completely discarded in the Meta backend.
The <protocol> part can be anything The <protocol> part can be anything
.BR ldap_initialize (3) .BR ldap_initialize (3)
accepts ({ldap|ldaps|ldapi} and variants); <host> and <port> may be accepts ({ldap|ldaps|ldapi} and variants); the <host> may be
omitted, defaulting to whatever is set in omitted, defaulting to whatever is set in
.BR ldap.conf (5). .BR ldap.conf (5).
The <naming context> part is mandatory. The <naming context> part is \fImandatory\fP for the first URI,
It must end with one of the naming contexts defined for the backend, but it \fImust be omitted\fP for subsequent ones, if any.
The naming context part must be within the naming context defined for the backend,
e.g.: e.g.:
.LP .LP
.RS .RS
@ -218,25 +217,25 @@ uri "ldap://x.foo.com/dc=x,\fBdc=foo,dc=com\fP"
.RS .RS
The <naming context> part doesn't need to be unique across the targets; The <naming context> part doesn't need to be unique across the targets;
it may also match one of the values of the "suffix" directive. it may also match one of the values of the "suffix" directive.
Multiple URIs may be defined in a single argument. The URIs must Multiple URIs may be defined in a single URI statement.
be separated by TABs (e.g. '\\t'; commas or spaces, unlike back-ldap, The URIs must be separate arguments and must not have any
will not work, <naming context> part. This causes the underlying library
because they are legal in the <naming context>, and we don't want to use
URL-encoded <naming context>s), and the additional URIs must have
no <naming context> part. This causes the underlying library
to contact the first server of the list that responds. to contact the first server of the list that responds.
For example, if \fIl1.foo.com\fP and \fIl2.foo.com\fP are shadows For example, if \fIl1.foo.com\fP and \fIl2.foo.com\fP are shadows
of the same server, the directive of the same server, the directive
.LP .LP
.nf .nf
suffix "\fBdc=foo,dc=com\fP" suffix "\fBdc=foo,dc=com\fP"
uri "ldap://l1.foo.com/\fBdc=foo,dc=com\fP ldap://l2.foo.com/" uri "ldap://l1.foo.com/\fBdc=foo,dc=com\fP" "ldap://l2.foo.com/"
.fi .fi
.RE .RE
.RS .RS
causes \fIl2.foo.com\fP to be contacted whenever \fIl1.foo.com\fP causes \fIl2.foo.com\fP to be contacted whenever \fIl1.foo.com\fP
does not respond. does not respond.
In that case, the URI list is internally rearranged, by moving unavailable
URIs to the end, so that further connection attempts occur with respect to
the last URI that succeeded.
.RE .RE
.TP .TP