Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenLDAP
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue 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
Jaak Ristioja
OpenLDAP
Commits
a9ed17a4
Commit
a9ed17a4
authored
20 years ago
by
Pierangelo Masarati
Browse files
Options
Downloads
Patches
Plain Diff
fix ITS#3441
parent
889b20e3
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/man/man5/slapd.conf.5
+3
-3
3 additions, 3 deletions
doc/man/man5/slapd.conf.5
with
3 additions
and
3 deletions
doc/man/man5/slapd.conf.5
+
3
−
3
View file @
a9ed17a4
...
...
@@ -1477,9 +1477,9 @@ If an error occurs during replication, the consumer will attempt to
reconnect according to the
.B retry
parameter which is a list of the <retry interval> and <# of retries> pairs.
For example, retry="60
5
300 3" lets the consumer retry every 60 seconds
for the first 10 times and then retry every 300 seconds for the next
three
times before stop retrying.
+
in <# of retries> means indefinite
For example, retry="60
10
300 3" lets the consumer retry every 60 seconds
for the first 10 times and then retry every 300 seconds for the next
3
times before stop retrying.
The `+'
in <# of retries> means indefinite
number of retries until success.
The schema checking can be enforced at the LDAP Sync
consumer site by turning on the
...
...
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