Bug: 147157

Fix Description: There was already a flag to disable the tombstone reap
thread, but there was no way to set it from outside the replica code.
I added some functions to set the flag, and to query it to show it
in the status entry.  When a total update request comes in, the flag
is set to disable, and when the total update ends for whatever reason
(success, error, connection terminated), the flag is set back to
enable.
In addition, the tombstone reap thread was being started after 1 hour -
this is too long and needed to be shorter.  We already have the
tombstone reap interval, so I changed it so that the reap thread
starts after this interval, then runs after every interval elapses.

1 files changed, 1 insertions, 0 deletions

diff --git a/ldap/servers/plugins/replication/repl5.h b/ldap/servers/plugins/replication/repl5.h
index d936cbea..f5d6943a 100644
--- a/ldap/servers/plugins/replication/repl5.h
+++ b/ldap/servers/plugins/replication/repl5.h
@@ -429,6 +429,7 @@ void replica_write_ruv (Replica *r);
 #define REPLICA_AGREEMENTS_DISABLED 8 /* Replica is offline */
 PRBool replica_is_state_flag_set(Replica *r, PRInt32 flag);
 void replica_set_state_flag (Replica *r, PRUint32 flag, PRBool clear); 
+void replica_set_tombstone_reap_stop(Replica *r, PRBool val);
 void replica_enable_replication (Replica *r);
 void replica_disable_replication (Replica *r, Object *r_obj);
 int replica_start_agreement(Replica *r, Repl_Agmt *ra);