summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/locking/oplocks.xml
blob: 46c0e5c4380f23ea35152f5030572ce201a367c1 (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
<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>