sorry if I was not clear enough, I will update the doc, but let me try to explain hereHi Ludwig,
On 09/29/2016 05:43 AM, Ludwig Krispenz wrote:
This is the initial proposal, thanks for your feedback
Please help me understanding the design...
I'm having a bit hard time to figure out the relationship/dependency among these 3 config parameters.
no. the primary parameter is: nsslapd-replica-accept-updates-state
Are they independent or dependent? Do they take any combinations -- 2 * 3 * 2 == 12.
that is a good question, there is the option to choose the default by what is "my" recommendation (auto: on, delay: n) or what is backward compatible (no change in default behaviour: auto off, delay: 0)
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,
_______________________________________________ 389-devel mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com
-- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander