MAN page from Mandrake Other ldap-servers-3.3-3.i386.rpm

SLAPD.REPLOG

Section: File Formats (5)
Updated: 11 April 1995
Index

NAME

slapd.replog - slapd replication log format

SYNOPSIS

slapd.replogslapd.replog.lock

DESCRIPTION

The file slapd.replog is produced by the stand-alone LDAP daemon,slapd,when changes are made to its local database that are to bepropagated to one or more replicaslapds.The file consists ofzero or more records, each one corresponding to a change, addition,or deletion from theslapddatabase. The file is meant to be readand processed byslurpd,the stand-alone LDAP update replication daemon. The records areseparated by a blank line. Each record has the following format.

The record begins with one or more lines indicating the replicasto which the change is to be propagated:

        replica: <hostname[:portnumber]>

Next, the time the change took place given, as the number of seconds since00:00:00 GMT, Jan. 1, 1970, with an optional decimal extension, in orderto make times unique. Note that slapd does not make times unique, butslurpd makes all times unique in its copies of the replog files.

        time: <integer[.integer]>

Next, the distinguished name of the entry being changed is given:

        dn: <distinguishedname>

Next, the type of change being made is given:

        changetype: <[modify|add|delete|modrdn]>

Finally, the change information itself is given, the format of whichdepends on what kind of change was specified above. For a changetypeof modify, the format is one or more of the following:

        add: <attributetype>        <attributetype>: <value1>        <attributetype>: <value2>        ...        -

Or, for a replace modification:

        replace: <attributetype>        <attributetype>: <value1>        <attributetype>: <value2>        ...        -

Or, for a delete modification:

        delete: <attributetype>        <attributetype>: <value1>        <attributetype>: <value2>        ...        -

If no attributetype lines are given, the entire attribute is to bedeleted.

For a changetype of add, the format is:

        <attributetype1>: <value1>        <attributetype1>: <value2>        ...        <attributetypeN>: <value1>        <attributetypeN>: <value2>

For a changetype of modrdn, the format is:

        newrdn: <newrdn>        deleteoldrdn: 0 | 1

where a value of 1 for deleteoldrdn means to delete the valuesforming the old rdn from the entry, and a value of 0 means toleave the values as non-distinguished attributes in the entry.

For a changetype of delete, no additional informationis needed in the record.

The format of the values is the LDAP Directory Interchange Formatdescribed inldif(5).

Access to the slapd.replog file is synchronized through theuse offlock(3)on the file slapd.replog.lock. Any processreading or writing this file should obey this locking convention.

EXAMPLE

The following sample slapd.replog file contains informationon one of each type of change.

        replica: truelies.rs.itd.umich.edu        replica: judgmentday.rs.itd.umich.edu        time: 797612941        dn: cn=Babs Jensen, o=U of M, c=US        changetype: add        objectclass: person        cn: babs        cn: babs jensen        sn: jensen                 replica: truelies.rs.itd.umich.edu        replica: judgmentday.rs.itd.umich.edu        time: 797612973        dn: cn=Babs Jensen, o=U of M, c=US        changetype: modify        add: description        description: the fabulous babs                 replica: truelies.rs.itd.umich.edu        replica: judgmentday.rs.itd.umich.edu        time: 797613020        dn: cn=Babs Jensen, o=U of M, c=US        changetype: modrdn        newrdn: cn=Barbara J Jensen        deleteoldrdn: 0

FILES