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)

1 files changed, 28 insertions, 0 deletions

diff --git a/docs/smbdotconf/locking/oplocks.xml b/docs/smbdotconf/locking/oplocks.xml
new file mode 100644
index 0000000000..46c0e5c438
--- /dev/null
+++ b/docs/smbdotconf/locking/oplocks.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="oplocks"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://samba.org/common">
+<description>
+	<para>This boolean option tells <command moreinfo="none">smbd</command> whether to 
+	issue oplocks (opportunistic locks) to file open requests on this 
+	share. The oplock code can dramatically (approx. 30% or more) improve 
+	the speed of access to files on Samba servers. It allows the clients 
+	to aggressively cache files locally and you may want to disable this 
+	option for unreliable network environments (it is turned on by 
+	default in Windows NT Servers).  For more information see the file 
+	<filename moreinfo="none">Speed.txt</filename> in the Samba <filename moreinfo="none">docs/</filename> 
+	directory.</para>
+
+	<para>Oplocks may be selectively turned off on certain files with a 
+	share. See the <link linkend="VETOOPLOCKFILES"><parameter moreinfo="none">
+	veto oplock files</parameter></link> parameter. On some systems 
+	oplocks are recognized by the underlying operating system. This 
+	allows data synchronization between all access to oplocked files, 
+	whether it be via Samba or NFS or a local UNIX process. See the 
+	<parameter moreinfo="none">kernel oplocks</parameter> parameter for details.</para>
+</description>
+
+<related>kernel oplocks</related>
+<related>level2 oplocks</related>
+<value type="default">yes</value>
+</samba:parameter>