DESCRIPTION
The file slapd.replog is produced by the stand-alone LDAP
daemon, slapd(8), when changes are
made to its local database that are to be propagated to one
or more replica slapds. The file consists of
zero or more records, each one corresponding to a change,
addition, or deletion from the slapd database. The file is
meant to be read and processed by slurpd(8), the stand-alone
LDAP update replication daemon. The records are separated by
a blank line. Each record has the following format.
The record begins with one or more lines indicating the
replicas to which the change is to be propagated:
Next, the time the change took place given, as the number
of seconds since 00:00:00 GMT, Jan. 1, 1970, with an optional
decimal extension, in order to make times unique. Note that
slapd does not make times unique, but slurpd makes all times
unique in its copies of the replog files.
Next, the distinguished name of the entry being changed is
given:
Next, the type of change being made is given:
Finally, the change information itself is given, the
format of which depends on what kind of change was specified
above. For a changetype of modify, the format is one or
more of the following:
Or, for a replace modification:
Or, for a delete modification:
If no attributetype lines are
given, the entire attribute is to be deleted.
For a changetype
of add, the format
is:
For a changetype
of modrdn, the
format is:
where a value of 1 for deleteoldrdn means to delete the
values forming the old rdn from the entry, and a value of 0
means to leave the values as non-distinguished attributes in
the entry.
For a changetype
of delete, no
additional information is needed in the record.
The format of the values is the LDAP Directory Interchange
Format described in ldif(5).
Access to the slapd.replog file is
synchronized through the use of flock(3) on the file slapd.replog.lock. Any
process reading or writing this file should obey this locking
convention.