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
3e3e5fde
Commit
3e3e5fde
authored
22 years ago
by
Pierangelo Masarati
Browse files
Options
Downloads
Patches
Plain Diff
first cut at documenting back-monitor
parent
426ca14a
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-monitor.5
+90
-0
90 additions, 0 deletions
doc/man/man5/slapd-monitor.5
with
90 additions
and
0 deletions
doc/man/man5/slapd-monitor.5
0 → 100644
+
90
−
0
View file @
3e3e5fde
.TH SLAPD-MONITOR 5 "RELEASEDATE" "OpenLDAP LDVERSION"
.\" Copyright 1998-2003 The OpenLDAP Foundation All Rights Reserved.
.\" Copying restrictions apply. See COPYRIGHT/LICENSE.
.\" $OpenLDAP$
.SH NAME
slapd-monitor \- Monitor backend to slapd
.SH SYNOPSIS
ETCDIR/slapd.conf
.SH DESCRIPTION
The monitor backend to
.BR slapd (8)
is not an actual database; if enabled, it is automatically generated
and maintained by slapd with information about the running status of
the daemon.
.SH CONFIGURATION
These
.B slapd.conf
options apply to the monitor backend database.
That is, they must follow a "database monitor" line and come before any
subsequent "backend" or "database" lines.
As opposed to most databases, the monitor database can be instantiated
only once, i.e. only one occurrence of "database monitor" can occur
in the
.BR slapd.conf (5)
file.
Moreover, the suffix of the database cannot be explicitly set by means
of the
.B suffix
directive; on the contrary, the suffix is automatically set to
.BR cn=Monitor .
No specific database directives can be specified.
The
.B monitor
database honors the
.B rootdn
and the
.B rootpw
directives, and the usual ACL directives, e.g. the
.B access
directive.
Other database options are described in the
.BR slapd.conf (5)
manual page.
.SH USAGE
The usage is:
1) enable the monitor backend at configure:
.LP
.RS
.nf
configure --enable-monitor
.fi
.RE
.LP
2) activate the monitor database in the
.BR slapd.conf (5)
file:
.LP
.RS
.nf
database monitor
.fi
.RE
.LP
3) add ACLs as detailed in
.BR slapd.access (5)
to control access to the database:
.LP
.RS
.nf
access to dn.subtree="cn=Monitor"
by dn.exact="uid=Admin,dc=my,dc=org" write
by users read
by * none
.fi
.RE
.LP
.SH FILES
.TP
ETCDIR/slapd.conf
default slapd configuration file
.SH SEE ALSO
.BR slapd.conf (5),
.BR slapd.access (5),
.BR slapd (8),
.BR ldap (3).
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