summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/locking/kerneloplocks.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/docbook/smbdotconf/locking/kerneloplocks.xml')
-rw-r--r--docs/docbook/smbdotconf/locking/kerneloplocks.xml27
1 files changed, 0 insertions, 27 deletions
diff --git a/docs/docbook/smbdotconf/locking/kerneloplocks.xml b/docs/docbook/smbdotconf/locking/kerneloplocks.xml
deleted file mode 100644
index f155fddc8f..0000000000
--- a/docs/docbook/smbdotconf/locking/kerneloplocks.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-<samba:parameter name="kernel oplocks"
- context="G"
- xmlns:samba="http://samba.org/common">
-<listitem>
- <para>For UNIXes that support kernel based <link linkend="OPLOCKS">
- <parameter moreinfo="none">oplocks</parameter></link>
- (currently only IRIX and the Linux 2.4 kernel), this parameter
- allows the use of them to be turned on or off.</para>
-
- <para>Kernel oplocks support allows Samba <parameter moreinfo="none">oplocks
- </parameter> to be broken whenever a local UNIX process or NFS operation
- accesses a file that <citerefentry><refentrytitle>smbd</refentrytitle>
- <manvolnum>8</manvolnum></citerefentry> has oplocked. This allows complete
- data consistency between SMB/CIFS, NFS and local file access (and is
- a <emphasis>very</emphasis> cool feature :-).</para>
-
- <para>This parameter defaults to <constant>on</constant>, but is translated
- to a no-op on systems that no not have the necessary kernel support.
- You should never need to touch this parameter.</para>
-
- <para>See also the <link linkend="OPLOCKS"><parameter moreinfo="none">oplocks</parameter>
- </link> and <link linkend="LEVEL2OPLOCKS"><parameter moreinfo="none">level2 oplocks
- </parameter></link> parameters.</para>
-
- <para>Default: <command moreinfo="none">kernel oplocks = yes</command></para>
-</listitem>
-</samba:parameter>