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
eb631657
Commit
eb631657
authored
23 years ago
by
Kurt Zeilenga
Browse files
Options
Downloads
Patches
Plain Diff
Minor fixes including those from ITS#1283
parent
a2ba804e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
doc/guide/admin/install.sdf
+4
-4
4 additions, 4 deletions
doc/guide/admin/install.sdf
doc/guide/admin/schema.sdf
+1
-1
1 addition, 1 deletion
doc/guide/admin/schema.sdf
doc/guide/admin/slapdconfig.sdf
+16
-9
16 additions, 9 deletions
doc/guide/admin/slapdconfig.sdf
with
21 additions
and
14 deletions
doc/guide/admin/install.sdf
+
4
−
4
View file @
eb631657
...
...
@@ -118,14 +118,14 @@ or the {{ORG[expand]FSF}}'s {{PRD:GNU}} Database Manager ({{PRD:GDBM}}).
If neither of these packages are available at configure time,
you will not be able build {{slapd}}(8) with primary database backend.
Your operating system may provide one of these
two
packages in
the base system or as an optional software component.
You may
need may need to obtain the software and install it
yourself.
Your operating system may provide one
or both
of these packages in
the base system or as an optional software component.
If not,
you'll have to obtain and install one of these packages
yourself.
{{PRD:BerkeleyDB}} is available from {{ORG[expand]Sleepy}}'s
download page {{URL: http://www.sleepycat.com/download.html}}.
There are several versions available. At the time of this writing,
the latest release, version 3.
1
, is recommended.
the latest release, version 3.
3
, is recommended.
{{PRD:GDBM}} is available from {{ORG:FSF}}'s download site
{{URL: ftp://ftp.gnu.org/pub/gnu/gdbm/}}.
...
...
This diff is collapsed.
Click to expand it.
doc/guide/admin/schema.sdf
+
1
−
1
View file @
eb631657
...
...
@@ -37,7 +37,7 @@ openldap.schema OpenLDAP Project (experimental)
!endblock
To use any of these schema files, you only need to include the
the
desired file in the global definitions portion of your
desired file in the global definitions portion of your
{{slapd.conf}}(5) file. For example:
> # include schema
...
...
This diff is collapsed.
Click to expand it.
doc/guide/admin/slapdconfig.sdf
+
16
−
9
View file @
eb631657
...
...
@@ -475,7 +475,6 @@ This directive specifies the indexes to maintain for the given
attribute. If only an {{EX:<attrlist>}} is given, the default
indexes are maintained.
\Example:
> index default pres,eq
...
...
@@ -491,6 +490,13 @@ be maintained for {{EX:cn}} and {{EX:sn}} attribute types. The
fourth line causes an equality index for the {{EX:objectClass}}
attribute type.
By default, no indices are maintained. It is generally advised
that minimally an equality index upon objectClass be maintained.
> index objectClass eq
H4: mode <integer>
This directive specifies the file protection mode that newly
...
...
@@ -861,12 +867,12 @@ Lines 9 and 10 identify the database "super user" entry and associated
password. This entry is not subject to access control or size or
time limit restrictions.
Lines 11 through 18 are for replication. Line 1
1
specifies the
Lines 11 through 18 are for replication. Line 1
2
specifies the
replication log file (where changes to the database are logged \-
this file is written by slapd and read by slurpd). Lines 1
2
through
1
4
specify the hostname and port for a replicated host, the DN to
this file is written by slapd and read by slurpd). Lines 1
3
through
1
5
specify the hostname and port for a replicated host, the DN to
bind as when performing updates, the bind method (simple) and the
credentials (password) for the binddn. Lines 1
5
through 18 specify
credentials (password) for the binddn. Lines 1
6
through 18 specify
a second replication site. See the {{SECT:Replication with slurpd}}
chapter for more information on these directives.
...
...
@@ -884,13 +890,14 @@ entry, but may be read by all users (authenticated or not).
The next section of the example configuration file defines another
LDBM database. This one handles queries involving the
{{EX:dc=example,dc=net}} subtree
. Note that without line 38, the
read access would be allowed due to the global access rule at line
4.
{{EX:dc=example,dc=net}} subtree
but is managed by the same entity
as the first database. Note that without line 39, the read access
would be allowed due to the global access rule at line
4.
E: 33. # ldbm definition for example.net
E: 34. database ldbm
E: 35. suffix "dc=example,dc=net"
E: 36. directory /usr/local/var/ldbm-example-net
E: 37. rootdn "cn=Manager,dc=example,dc=com"
E: 38. access to * by users read
E: 38. index objectClass eq
E: 39. access to * by users read
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