Hi Ludwig,

On 09/29/2016 05:43 AM, Ludwig Krispenz wrote:
This is the initial proposal, thanks for your feedback

http://www.port389.org/docs/389ds/design/delay-accepting-updates-after-init.html

Please help me understanding the design...

I'm having a bit hard time to figure out the relationship/dependency among these 3 config parameters.

nsslapd-replica-accept-updates-state: on/off
nsslapd-replica-accept-updates-delay: -1/0/n
nsslapd-replica-accept-updates-auto: on/off

Are they independent or dependent?  Do they take any combinations -- 2 * 3 * 2 == 12.  There are 12 different behaviors?  (assuming n for -delay is one case :)

What is your recommendation to the customers?  I mean, what is the default setting?  For instance, if -auto is "on", when an online init is executed on the master, the scenario is automatically kicked in?

Thanks,
--noriko