diff options
author | John Terpstra <jht@samba.org> | 2005-08-25 16:49:40 +0000 |
---|---|---|
committer | Gerald W. Carter <jerry@samba.org> | 2008-04-23 08:47:06 -0500 |
commit | 6c2e58987bcb3b5fe527f7f6743c549ed6c0c877 (patch) | |
tree | 700bab687907526be31f9dcadc1e826845562a7b /docs/smbdotconf/ldap/ldapreplicationsleep.xml | |
parent | cf596ff9a0e5e191cfdc5f219e57844ad35ba7a2 (diff) | |
download | samba-6c2e58987bcb3b5fe527f7f6743c549ed6c0c877.tar.gz samba-6c2e58987bcb3b5fe527f7f6743c549ed6c0c877.tar.bz2 samba-6c2e58987bcb3b5fe527f7f6743c549ed6c0c877.zip |
Formatting and other fixes to man pages.
(This used to be commit 411025ed0d6ba37ff00f4afc8ccdc9dae94b62e0)
Diffstat (limited to 'docs/smbdotconf/ldap/ldapreplicationsleep.xml')
-rw-r--r-- | docs/smbdotconf/ldap/ldapreplicationsleep.xml | 30 |
1 files changed, 16 insertions, 14 deletions
diff --git a/docs/smbdotconf/ldap/ldapreplicationsleep.xml b/docs/smbdotconf/ldap/ldapreplicationsleep.xml index b1a24d2af8..4710e2b3b3 100644 --- a/docs/smbdotconf/ldap/ldapreplicationsleep.xml +++ b/docs/smbdotconf/ldap/ldapreplicationsleep.xml @@ -4,20 +4,22 @@ type="integer" xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> <description> - <para>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. </para> - <para>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.</para> - <para>The value is specified in milliseconds, the maximum -value is 5000 (5 seconds).</para> + <para> + 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. + </para> + + <para> + 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. + </para> + + <para> + The value is specified in milliseconds, the maximum value is 5000 (5 seconds). + </para> </description> <value type="default">1000</value> </samba:parameter> |