1 .TH SLAPD.REPLOG 5 "22 September 1998" "OpenLDAP LDVERSION"
3 slapd.replog \- slapd replication log format
9 The file slapd.replog is produced by the stand-alone LDAP daemon,
11 when changes are made to its local database that are to be
12 propagated to one or more replica
15 zero or more records, each one corresponding to a change, addition,
18 database. The file is meant to be read
21 the stand-alone LDAP update replication daemon. The records are
22 separated by a blank line. Each record has the following format.
24 The record begins with one or more lines indicating the replicas
25 to which the change is to be propagated:
28 replica: <hostname[:portnumber]>
31 Next, the time the change took place given, as the number of seconds since
32 00:00:00 GMT, Jan. 1, 1970, with an optional decimal extension, in order
33 to make times unique. Note that slapd does not make times unique, but
34 slurpd makes all times unique in its copies of the replog files.
37 time: <integer[.integer]>
40 Next, the distinguished name of the entry being changed is given:
43 dn: <distinguishedname>
46 Next, the type of change being made is given:
49 changetype: <[modify|add|delete|modrdn]>
52 Finally, the change information itself is given, the format of which
53 depends on what kind of change was specified above. For a \fIchangetype\fP
54 of \fImodify\fP, the format is one or more of the following:
58 <attributetype>: <value1>
59 <attributetype>: <value2>
64 Or, for a replace modification:
67 replace: <attributetype>
68 <attributetype>: <value1>
69 <attributetype>: <value2>
74 Or, for a delete modification:
77 delete: <attributetype>
78 <attributetype>: <value1>
79 <attributetype>: <value2>
84 If no \fIattributetype\fP lines are given, the entire attribute is to be
87 For a \fIchangetype\fP of \fIadd\fP, the format is:
90 <attributetype1>: <value1>
91 <attributetype1>: <value2>
93 <attributetypeN>: <value1>
94 <attributetypeN>: <value2>
97 For a \fIchangetype\fP of \fImodrdn\fP, the format is:
104 where a value of 1 for deleteoldrdn means to delete the values
105 forming the old rdn from the entry, and a value of 0 means to
106 leave the values as non-distinguished attributes in the entry.
108 For a \fIchangetype\fP of \fIdelete\fP, no additional information
109 is needed in the record.
111 The format of the values is the LDAP Directory Interchange Format
115 Access to the \fIslapd.replog\fP file is synchronized through the
118 on the file \fIslapd.replog.lock\fP. Any process
119 reading or writing this file should obey this locking convention.
121 The following sample \fIslapd.replog\fP file contains information
122 on one of each type of change.
125 replica: truelies.rs.itd.umich.edu
126 replica: judgmentday.rs.itd.umich.edu
128 dn: cn=Babs Jensen, o=U of M, c=US
135 replica: truelies.rs.itd.umich.edu
136 replica: judgmentday.rs.itd.umich.edu
138 dn: cn=Babs Jensen, o=U of M, c=US
141 description: the fabulous babs
143 replica: truelies.rs.itd.umich.edu
144 replica: judgmentday.rs.itd.umich.edu
146 dn: cn=Babs Jensen, o=U of M, c=US
148 newrdn: cn=Barbara J Jensen
161 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
163 is derived from University of Michigan LDAP 3.3 Release.