From 4f5791ebd03eaec1c7da0865a383175b05102712 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 5 May 2024 19:47:29 +0200 Subject: Adding upstream version 2:4.17.12+dfsg. Signed-off-by: Daniel Baumann --- docs-xml/smbdotconf/filename/vetooplockfiles.xml | 33 ++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 docs-xml/smbdotconf/filename/vetooplockfiles.xml (limited to 'docs-xml/smbdotconf/filename/vetooplockfiles.xml') 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 @@ + + + + This parameter is only valid when the + 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 + parameter. + + + + + 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 + .SEM. 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. + + + + An example of use is: + +veto oplock files = /.*SEM/ + + + +No files are vetoed for oplock grants + -- cgit v1.2.3