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/locking/kerneloplocks.xml | 29 +++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 docs-xml/smbdotconf/locking/kerneloplocks.xml (limited to 'docs-xml/smbdotconf/locking/kerneloplocks.xml') diff --git a/docs-xml/smbdotconf/locking/kerneloplocks.xml b/docs-xml/smbdotconf/locking/kerneloplocks.xml new file mode 100644 index 0000000..ff237ec --- /dev/null +++ b/docs-xml/smbdotconf/locking/kerneloplocks.xml @@ -0,0 +1,29 @@ + + + For UNIXes that support kernel based + (currently only Linux), this parameter allows the use of them to be + turned on or off. However, this disables Level II oplocks for clients as + the Linux kernel does not support them properly. + + Kernel oplocks support allows Samba oplocks + to be broken whenever a local UNIX process or NFS operation + accesses a file that smbd + 8 has oplocked. This allows complete + data consistency between SMB/CIFS, NFS and local file access (and is + a very cool feature :-). + If you do not need this interaction, you should disable the + parameter on Linux to get Level II oplocks and the associated + performance benefit. + + This parameter defaults to no and is translated + to a no-op on systems that do not have the necessary kernel support. + + +oplocks +level2 oplocks +smb2 leases +no + -- cgit v1.2.3