From c20c7bfec7853167f9ece7ad2ba59df0795f9e25 Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Tue, 24 Nov 2015 08:45:50 -0800 Subject: [PATCH] s3: docs: Fix "strict rename" doc to match code. BUG: https://bugzilla.samba.org/show_bug.cgi?id=11065 Signed-off-by: Jeremy Allison Reviewed-by: Michael Adam Autobuild-User(master): Jeremy Allison Autobuild-Date(master): Tue Nov 24 23:47:19 CET 2015 on sn-devel-104 (cherry picked from commit 2b0df3788aaadcf907de15a6b6a518244c59aa81) Autobuild-User(v4-3-test): Karolin Seeger Autobuild-Date(v4-3-test): Wed Jun 22 16:34:25 CEST 2016 on sn-devel-104 --- docs-xml/smbdotconf/tuning/strictrename.xml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/docs-xml/smbdotconf/tuning/strictrename.xml b/docs-xml/smbdotconf/tuning/strictrename.xml index 54788634d8d..91572f2994e 100644 --- a/docs-xml/smbdotconf/tuning/strictrename.xml +++ b/docs-xml/smbdotconf/tuning/strictrename.xml @@ -15,9 +15,18 @@ Samba system the cost is even greater than the non-clustered case. - For this reason the default is "no", and it is recommended - to be left that way unless a specific Windows application requires - it to be changed. + When set to "no" smbd only checks the local process + the client is attached to for open files below a directory + being renamed, instead of checking for open files across all + smbd processes. + + Because of the expense in fully searching the database, + the default is "no", and it is recommended to be left that way + unless a specific Windows application requires it to be changed. + + If the client has requested UNIX extensions (POSIX + pathnames) then renames are always allowed and this parameter + has no effect. -- 2.47.2