LDAP replication

Replication errors

When slurpd propagates a change to a slave slapd and receives an error return code, it writes the reason for the error and the replication record to a reject file. The reject file is located in the same directory with the per-replica replication log file, and has the same name, but with the string ``.rej'' appended. For example, for a replica running on host cayman.rs.itd.antbear.com, port 389, the reject file, if it exists, will be named as follows:

   /usr/tmp/cayman.rs.itd.antbear.com:389

A sample rejection log entry follows:

   ERROR: No such attribute
   replica: cayman.rs.itd.antbear.com:389
   time: 809618633
   dn: cn=Liam Q Antbear, ou=People, o=Antbear, Lucid & Popp, c=US
   changetype: modify
   delete: multiLineDescription
   multiLineDescription: I never give up
   -
   add: multiLineDescription
   multiLineDescription: Never feel pity
   -
   delete: lastModifiedBy
   -
   add: lastModifiedBy
   lastModifiedBy: cn=Liam Q Antbear, ou=People, o=Antbear, Lucid & Popp,
    c=US
   -
   delete: lastModifiedTime
   -
   add: lastModifiedTime
   lastModifiedTime: 950825073308Z
   -

Note that this is precisely the same format as the original replication log entry, but with an ERROR line prepended to the entry.