Adding upstream version 2:4.17.12+dfsg.upstream/2%4.17.12+dfsgupstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 29 insertions, 0 deletions

diff --git a/docs-xml/smbdotconf/filename/deletevetofiles.xml b/docs-xml/smbdotconf/filename/deletevetofiles.xml
new file mode 100644
index 0000000..570d4ac
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/deletevetofiles.xml
@@ -0,0 +1,29 @@
+<samba:parameter name="delete veto files"
+                 type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This option is used when Samba is attempting to 
+	delete a directory that contains one or more vetoed files
+	or directories or non-visible files or directories (such
+	as dangling symlinks that point nowhere).
+	(see the <smbconfoption name="veto files"/>, <smbconfoption name="hide special files"/>,
+	<smbconfoption name="hide unreadable"/>, <smbconfoption name="hide unwriteable files"/>
+	options).  If this option is set to <constant>no</constant> (the default) then if a vetoed
+	directory contains any non-vetoed files or directories then the 
+	directory delete will fail. This is usually what you want.</para>
+
+	<para>If this option is set to <constant>yes</constant>, then Samba 
+	will attempt to recursively delete any files and directories within 
+	the vetoed directory. This can be useful for integration with file 
+	serving systems such as NetAtalk which create meta-files within 
+	directories you might normally veto DOS/Windows users from seeing 
+	(e.g. <filename moreinfo="none">.AppleDouble</filename>)</para>
+
+	<para>Setting <smbconfoption name="delete veto files">yes</smbconfoption> allows these 
+	directories to be  transparently deleted when the parent directory 
+	is deleted (so long as the user has permissions to do so).</para>
+</description>
+<related>veto files</related>
+<value type="default">no</value>
+</samba:parameter>