So let's set I have the following option in my smb.conf


[share1]


path = /home/share1


veto files = /no-see*/


delete veto files = No




Now, I have the following directory structure:


/home/share1/yes-see1/


                   no-see-file1


                   no-see-file2




/home/share1/yes-see2/


                   no-see-dir/


                            no-see-file2




Delete veto files = No is only protecting the /home/shares/yes-see2 directory, 
and not the /home/share1/yes-see1 directory.




So the problem is Delete veto files doesn't work when the vetoed 
files/directories are a single level deep. 




Compounding this problem is the fact that the man page is very confusing, see 
below how the first and second sentences say very different things:


"option is used when Samba is attempting to delete a directory that contains one 
or more vetoed directories (see the veto files option). If this option is set to 
no (the default) then if a vetoed directory contains any non-vetoed files or 
directories then the directory delete will fail. 




The first sentence says that this is used when samba attempts to delete a 
directory (non-vetoed, I assume) that has vetoed directories inside of it. The 
second refers to a vetoed directory containing other vetoed directories. These 
are two very different cases.




I think that the delete veto files = no should prevent the case where you have a 
single vetoed file/directory inside a non-vetoed directory. And this part of the 
smb.conf man page from the veto files section seems to support that:


"One feature of the veto files parameter that it is important to be aware of is 
Samba's behaviour when trying to delete a directory. If a directory that is to 
be deleted contains nothing but veto files this deletion will fail unless you 
also set the delete veto files parameter to yes".