summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/locking/kerneloplocks.xml
blob: 98513fdd1e92ba3ebd212ffa15965c1989da8c84 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
<samba:parameter xmlns:samba="http://samba.org/common">
		<term><anchor id="KERNELOPLOCKS"/>kernel oplocks (G)</term>
		<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>