summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/tuning/strictallocate.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/docbook/smbdotconf/tuning/strictallocate.xml')
-rw-r--r--docs/docbook/smbdotconf/tuning/strictallocate.xml23
1 files changed, 0 insertions, 23 deletions
diff --git a/docs/docbook/smbdotconf/tuning/strictallocate.xml b/docs/docbook/smbdotconf/tuning/strictallocate.xml
deleted file mode 100644
index 0d11519b04..0000000000
--- a/docs/docbook/smbdotconf/tuning/strictallocate.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<samba:parameter name="strict allocate"
- context="S"
- xmlns:samba="http://samba.org/common">
-<listitem>
- <para>This is a boolean that controls the handling of
- disk space allocation in the server. When this is set to <constant>yes</constant>
- the server will change from UNIX behaviour of not committing real
- disk storage blocks when a file is extended to the Windows behaviour
- of actually forcing the disk system to allocate real storage blocks
- when a file is created or extended to be a given size. In UNIX
- terminology this means that Samba will stop creating sparse files.
- This can be slow on some systems.</para>
-
- <para>When strict allocate is <constant>no</constant> the server does sparse
- disk block allocation when a file is extended.</para>
-
- <para>Setting this to <constant>yes</constant> can help Samba return
- out of quota messages on systems that are restricting the disk quota
- of users.</para>
-
- <para>Default: <command moreinfo="none">strict allocate = no</command></para>
-</listitem>
-</samba:parameter>