summaryrefslogtreecommitdiffstats
path: root/docs-xml/smbdotconf/filename/vetooplockfiles.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs-xml/smbdotconf/filename/vetooplockfiles.xml')
-rw-r--r--docs-xml/smbdotconf/filename/vetooplockfiles.xml33
1 files changed, 33 insertions, 0 deletions
diff --git a/docs-xml/smbdotconf/filename/vetooplockfiles.xml b/docs-xml/smbdotconf/filename/vetooplockfiles.xml
new file mode 100644
index 0000000..8d6a922
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/vetooplockfiles.xml
@@ -0,0 +1,33 @@
+<samba:parameter name="veto oplock files"
+ context="S"
+ type="string"
+ substitution="1"
+ xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+ <para>
+ This parameter is only valid when the <smbconfoption name="oplocks"/>
+ 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
+ <smbconfoption name="veto files"/> 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>
+
+ <para>
+ An example of use is:
+<programlisting>
+veto oplock files = /.*SEM/
+</programlisting>
+ </para>
+</description>
+<value type="default"><comment>No files are vetoed for oplock grants</comment></value>
+</samba:parameter>