NAME
bdii - services
DESCRIPTION
Service: bdii-update
The Berkeley Database Information Index (BDII) consists of two or more
standard LDAP databases that are populated by an update process. Port
forwarding is used to enable one or more databases to serve data while
one database is being refreshed. The databases are refreshed
cyclically. Any incoming connection is forwarded to the most recently
updated database, while old connections are allowed to linger until it
is the turn of their database to be refreshed and restarted. The
update process obtains LDIF from either doing an ldapsearch on LDAP
URLs or by running a local script (given by a URL with file protocol)
that generates LDIF. The LDIF is then inserted into the LDAP database.
Options exist to update the list of LDAP URLs from a web page and to
use an LDIF file from a web page to modify the data before it is
inserted into the database.
Configuration files: bdii-update.conf, bdii.conf
Service: bdii-fwd
The BDII fwd service is a TCP port forwarder that redirects request on
the external service port to any of a set of backend ports, always
taking the port of the most up-to-date slapd. Old connections are
allowed to linger until their slapd is restarted. The bdii-fwd service
is only started by the bdii-update service, never directly. The
service is stopped by the bdii init script on terminating the bdii
service.
Configuration files: bdii-fwd.conf (generated by bdii-update)
Service: bdii-proxy
Script to generate a proxy derived from the host certificate, to be
made available to info providers that query secure services. It is
called once when the BDII is started and henceforth regularly by a cron
job.
Service: bdii
SystemV init script to start/stop the bdii-update service and the bdii-
related slapd daemons. It will write the slapd.conf configuration files
needed by the bdii slapd instances based on bdii.conf and the schemas
file.
Configuration files: bdii.conf, schemas