summaryrefslogtreecommitdiff
path: root/docs-xml/smbdotconf/locking/kerneloplocks.xml
blob: 8e3bba512268cd9b98954de3b97e90f1d533143f (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
25
26
27
28
29
<samba:parameter name="kernel oplocks"
				 type="boolean"
		 context="S"
                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
	<para>For UNIXes that support kernel based <smbconfoption name="oplocks"/>
	(currently only IRIX and the Linux 2.4 kernel), this parameter 
	allows the use of them to be turned on or off. However, this disables
	Level II oplocks for clients as the Linux and IRIX kernels do not
	support them properly.</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>If you do not need this interaction, you should disable the
	parameter on Linux and IRIX to get Level II oplocks and the associated
	performance benefit.</para>

	<para>This parameter defaults to <constant>no</constant> and is translated
	to a no-op on systems that do not have the necessary kernel support.</para>
</description>

<related>oplocks</related>
<related>level2 oplocks</related>
<value type="default">no</value>
</samba:parameter>