From 61fc3f7b085b325f84e434d082d6b471177d6914 Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Mon, 3 Nov 2014 14:56:04 -0800 Subject: [PATCH] WHATSNEW - document "strict rename". Signed-off-by: Jeremy Allison --- WHATSNEW.txt | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/WHATSNEW.txt b/WHATSNEW.txt index b1d8ee3..e8d4bcb 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -266,6 +266,24 @@ access with Netatalk 3. The modules behaviour is fully configurable, please refer to the manpage vfs_fruit for further details. +New per-share parameter "strict rename" +======================================= + +By default a Windows SMB server prevents directory renames when +there are open file or directory handles below it in the filesystem +hierarchy. Historically Samba has always allowed this as POSIX +filesystem semantics require it. + +This new boolean parameter allows Samba to match the Windows +behavior. Setting this to "yes" is a very expensive change, +as it forces Samba to travers the entire open file handle +database on every directory rename request. In a clustered +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. ###################################################################### Changes @@ -282,6 +300,7 @@ smb.conf changes reject md5 client New no reject md5 servers New no require strong key New yes + strict rename New no smb2 max read Changed default 8388608 smb2 max write Changed default 8388608 smb2 max trans Changed default 8388608 -- 2.1.0.rc2.206.gedb03e5