Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenLDAP
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Christopher Ng
OpenLDAP
Commits
f2f195ac
Commit
f2f195ac
authored
21 years ago
by
Kurt Zeilenga
Browse files
Options
Downloads
Patches
Plain Diff
Fix SDF warnings
parent
b0d7f59a
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/guide/admin/slapdconfig.sdf
+10
-10
10 additions, 10 deletions
doc/guide/admin/slapdconfig.sdf
with
10 additions
and
10 deletions
doc/guide/admin/slapdconfig.sdf
+
10
−
10
View file @
f2f195ac
...
...
@@ -470,10 +470,10 @@ H4: syncrepl
This directive specifies the current database as a replica of the
master database at the provider site. The replica database at the
replication consumer site is kept up-to-date with the master
database
using the LDAP Content Synchronization protocol.
See {{REF
:draft-zeilenga-ldup-sync-
04
.txt}}
for more information
on the protocol.
replication consumer site is kept up-to-date with the master
database
using the LDAP Content Synchronization protocol.
See
{{EX
:draft-zeilenga-ldup-sync-
xx
.txt}}
({{a work in progress}}) for
more information
on the protocol.
The {{EX:id}} parameter is used for identification of the current
syncrepl directive in the database, where the three-digit integer
...
...
@@ -493,15 +493,15 @@ specification is located at the provider site. {{EX:syncrepl}} and
{{EX:replica}} are two independent replication mechanisms and they do
not represent the replication peers of each other.
The content of the syncrepl replica is defined using a search
specification as its result set. The consumer slapd will
send
search requests to the provider slapd according to the search
The content of the
{{EX:
syncrepl
}}
replica is defined using a search
specification as its result set. The consumer
{{
slapd
}}(8)
will
send
search requests to the provider slapd according to the search
specification. The search specification includes {{EX:searchbase}},
{{EX:scope}}, {{EX:filter}}, {{EX:attrs}}, {{EX:attrsonly}},
{{EX:sizelimit}}, and {{EX:timelimit}} parameters as in the normal
search specification. The syncrepl search specification
has
the same value syntax and the same default values
as in the {{REF:
ldapsearch(1)
}}
client search tool.
search specification. The
{{EX:
syncrepl
}}
search specification
has
the same value syntax and the same default values
as in the
{{
ldapsearch
}}
(1) client search tool.
The LDAP Content Synchronization protocol has two operation
types: {{EX:refreshOnly}} and {{EX:refreshAndPersist}}.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment