First, OpenLDAP 2.0 is deprecated (no longer supported). You should
look at upgrading to a current version of OpenLDAP (2.2.13 or later).
i know that i have to do it but my current conf "do the job"
Second, slurpd only creates .rej files if the slave rejects a change.
If the slave is down, slurpd will simply keep adding the changes to its
replog file. What you can do in this case, is monitor the size of the
slurpd replog file, and then send out an alert when it grows to be above
a certain size.
so when the slave go online the master will replicate the changes ?