From 992f1e6b8f86b346fddd266b04d29cde69585633 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Wed, 7 Apr 2004 10:15:11 +0000 Subject: Add all the source files from the old CVS tree, add the 5 missing chapters from the HOWTO and add jht's Samba by Example book. (This used to be commit 9fb5bcb93e57c5162b3ee6f9c7d777dc0269d100) --- docs/smbdotconf/ldap/ldapreplicationsleep.xml | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 docs/smbdotconf/ldap/ldapreplicationsleep.xml (limited to 'docs/smbdotconf/ldap/ldapreplicationsleep.xml') diff --git a/docs/smbdotconf/ldap/ldapreplicationsleep.xml b/docs/smbdotconf/ldap/ldapreplicationsleep.xml new file mode 100644 index 0000000000..9630273501 --- /dev/null +++ b/docs/smbdotconf/ldap/ldapreplicationsleep.xml @@ -0,0 +1,22 @@ + + + When Samba is asked to write to a read-only LDAP +replica, we are redirected to talk to the read-write master server. +This server then replicates our changes back to the 'local' server, +however the replication might take some seconds, especially over slow +links. Certain client activities, particularly domain joins, can become +confused by the 'success' that does not immediately change the LDAP +back-end's data. + This option simply causes Samba to wait a short time, to +allow the LDAP server to catch up. If you have a particularly +high-latency network, you may wish to time the LDAP replication with a +network sniffer, and increase this value accordingly. Be aware that no +checking is performed that the data has actually replicated. + The value is specified in milliseconds + +1000 + -- cgit