summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/filename/vetooplockfiles.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/smbdotconf/filename/vetooplockfiles.xml')
-rw-r--r--docs/smbdotconf/filename/vetooplockfiles.xml25
1 files changed, 25 insertions, 0 deletions
diff --git a/docs/smbdotconf/filename/vetooplockfiles.xml b/docs/smbdotconf/filename/vetooplockfiles.xml
new file mode 100644
index 0000000000..6f546ecc16
--- /dev/null
+++ b/docs/smbdotconf/filename/vetooplockfiles.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="veto oplock files"
+ context="S"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+ <description>
+ <para>This parameter is only valid when the <link linkend="OPLOCKS">
+ <parameter moreinfo="none">oplocks</parameter></link>
+ parameter is turned on for a share. It allows the Samba administrator
+ to selectively turn off the granting of oplocks on selected files that
+ match a wildcarded list, similar to the wildcarded list used in the
+ <link linkend="VETOFILES"><parameter moreinfo="none">veto files</parameter></link>
+ parameter.</para>
+
+
+ <para>You might want to do this on files that you know will
+ be heavily contended for by clients. A good example of this
+ is in the NetBench SMB benchmark program, which causes heavy
+ client contention for files ending in <filename moreinfo="none">.SEM</filename>.
+ To cause Samba not to grant oplocks on these files you would use
+ the line (either in the [global] section or in the section for
+ the particular NetBench share :</para>
+</description>
+<value type="default"><comment>No files are vetoed for oplock grants</comment></value>
+<value type="example">/.*SEM/</value>
+</samba:parameter>