diff options
Diffstat (limited to 'docs/smbdotconf/filename')
22 files changed, 445 insertions, 0 deletions
diff --git a/docs/smbdotconf/filename/casesensitive.xml b/docs/smbdotconf/filename/casesensitive.xml new file mode 100644 index 0000000000..4520ff80e9 --- /dev/null +++ b/docs/smbdotconf/filename/casesensitive.xml @@ -0,0 +1,10 @@ +<samba:parameter name="case sensitive" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<synonym>casesignames</synonym> +<description> + <para>See the discussion in the section <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link>.</para> +</description> +<value type="default">no</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/defaultcase.xml b/docs/smbdotconf/filename/defaultcase.xml new file mode 100644 index 0000000000..959959205b --- /dev/null +++ b/docs/smbdotconf/filename/defaultcase.xml @@ -0,0 +1,10 @@ +<samba:parameter name="default case" + context="S" + type="string" xmlns:samba="http://samba.org/common"> +<description> + <para>See the section on <link linkend="NAMEMANGLINGSECT"> + NAME MANGLING</link>. Also note the <link linkend="SHORTPRESERVECASE"> + <parameter moreinfo="none">short preserve case</parameter></link> parameter.</para> +</description> +<value type="default">lower</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/deletevetofiles.xml b/docs/smbdotconf/filename/deletevetofiles.xml new file mode 100644 index 0000000000..69821392d7 --- /dev/null +++ b/docs/smbdotconf/filename/deletevetofiles.xml @@ -0,0 +1,26 @@ +<samba:parameter name="delete veto files" + type="boolean" + context="S" + xmlns:samba="http://samba.org/common"> +<description> + <para>This option is used when Samba is attempting to + delete a directory that contains one or more vetoed directories + (see the <link linkend="VETOFILES"><parameter moreinfo="none">veto files</parameter></link> + option). 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 <command moreinfo="none">delete veto files = yes</command> 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> diff --git a/docs/smbdotconf/filename/hidedotfiles.xml b/docs/smbdotconf/filename/hidedotfiles.xml new file mode 100644 index 0000000000..7aa5145a9a --- /dev/null +++ b/docs/smbdotconf/filename/hidedotfiles.xml @@ -0,0 +1,10 @@ +<samba:parameter name="hide dot files" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This is a boolean parameter that controls whether + files starting with a dot appear as hidden files.</para> +</description> +<value type="default">yes</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/hidefiles.xml b/docs/smbdotconf/filename/hidefiles.xml new file mode 100644 index 0000000000..5486b13b69 --- /dev/null +++ b/docs/smbdotconf/filename/hidefiles.xml @@ -0,0 +1,37 @@ +<samba:parameter name="hide files" + type="string" + context="S" + xmlns:samba="http://samba.org/common"> +<description> + <para>This is a list of files or directories that are not + visible but are accessible. The DOS 'hidden' attribute is applied + to any files or directories that match.</para> + + <para>Each entry in the list must be separated by a '/', + which allows spaces to be included in the entry. '*' + and '?' can be used to specify multiple files or directories + as in DOS wildcards.</para> + + <para>Each entry must be a Unix path, not a DOS path and must + not include the Unix directory separator '/'.</para> + + <para>Note that the case sensitivity option is applicable + in hiding files.</para> + + <para>Setting this parameter will affect the performance of Samba, + as it will be forced to check all files and directories for a match + as they are scanned.</para> +</description> + +<related>hide dot files</related> +<related>veto files</related> +<related>case sensitive</related> + +<value type="default"><comment>no file are hidden</comment></value> +<value type="example">/.*/DesktopFolderDB/TrashFor%m/resource.frk/<comment> +The above example is based on files that the Macintosh +SMB client (DAVE) available from <ulink url="http://www.thursby.com"> +Thursby</ulink> creates for internal use, and also still hides +all files beginning with a dot.</comment></value> + +</samba:parameter> diff --git a/docs/smbdotconf/filename/hidespecialfiles.xml b/docs/smbdotconf/filename/hidespecialfiles.xml new file mode 100644 index 0000000000..dd7ba12bee --- /dev/null +++ b/docs/smbdotconf/filename/hidespecialfiles.xml @@ -0,0 +1,12 @@ +<samba:parameter name="hide special files" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This parameter prevents clients from seeing + special files such as sockets, devices and fifo's in directory + listings. +</para> +</description> +<value type="default">no</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/hideunreadable.xml b/docs/smbdotconf/filename/hideunreadable.xml new file mode 100644 index 0000000000..40e831128a --- /dev/null +++ b/docs/smbdotconf/filename/hideunreadable.xml @@ -0,0 +1,10 @@ +<samba:parameter name="hide unreadable" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> + <description> + <para>This parameter prevents clients from seeing the + existance of files that cannot be read. Defaults to off.</para> +</description> +<value type="default">no</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/hideunwriteablefiles.xml b/docs/smbdotconf/filename/hideunwriteablefiles.xml new file mode 100644 index 0000000000..6b4f7cceb8 --- /dev/null +++ b/docs/smbdotconf/filename/hideunwriteablefiles.xml @@ -0,0 +1,12 @@ +<samba:parameter name="hide unwriteable files" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This parameter prevents clients from seeing + the existance of files that cannot be written to. Defaults to off. + Note that unwriteable directories are shown as usual. +</para> +</description> +<value type="default">no</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/manglecase.xml b/docs/smbdotconf/filename/manglecase.xml new file mode 100644 index 0000000000..269eb68e97 --- /dev/null +++ b/docs/smbdotconf/filename/manglecase.xml @@ -0,0 +1,9 @@ +<samba:parameter name="mangle case" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>See the section on <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link></para> +</description> +<value type="default">no</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/mangledmap.xml b/docs/smbdotconf/filename/mangledmap.xml new file mode 100644 index 0000000000..c195fb6688 --- /dev/null +++ b/docs/smbdotconf/filename/mangledmap.xml @@ -0,0 +1,26 @@ +<samba:parameter name="mangled map" + type="string" + context="S" + xmlns:samba="http://samba.org/common"> +<description> + <para>This is for those who want to directly map UNIX + file names which cannot be represented on Windows/DOS. The mangling + of names is not always what is needed. In particular you may have + documents with file extensions that differ between DOS and UNIX. + For example, under UNIX it is common to use <filename moreinfo="none">.html</filename> + for HTML files, whereas under Windows/DOS <filename moreinfo="none">.htm</filename> + is more commonly used.</para> + + <para>So to map <filename moreinfo="none">html</filename> to <filename moreinfo="none">htm</filename> + you would use:</para> + + <para><command moreinfo="none">mangled map = (*.html *.htm)</command></para> + + <para>One very useful case is to remove the annoying <filename moreinfo="none">;1 + </filename> off the ends of filenames on some CDROMs (only visible + under some UNIXes). To do this use a map of (*;1 *;).</para> +</description> + +<value type="default"><comment>no mangled map</comment></value> +<value type="example">(*;1 *;)</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/manglednames.xml b/docs/smbdotconf/filename/manglednames.xml new file mode 100644 index 0000000000..6ee6e11073 --- /dev/null +++ b/docs/smbdotconf/filename/manglednames.xml @@ -0,0 +1,67 @@ +<samba:parameter name="mangled names" + type="boolean" + context="S" + xmlns:samba="http://samba.org/common"> +<description> + <para>This controls whether non-DOS names under UNIX + should be mapped to DOS-compatible names ("mangled") and made visible, + or whether non-DOS names should simply be ignored.</para> + + <para>See the section on <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link> for + details on how to control the mangling process.</para> + + <para>If mangling is used then the mangling algorithm is as follows:</para> + + <itemizedlist> + <listitem> + <para>The first (up to) five alphanumeric characters + before the rightmost dot of the filename are preserved, forced + to upper case, and appear as the first (up to) five characters + of the mangled name.</para> + </listitem> + + <listitem> + <para>A tilde "~" is appended to the first part of the mangled + name, followed by a two-character unique sequence, based on the + original root name (i.e., the original filename minus its final + extension). The final extension is included in the hash calculation + only if it contains any upper case characters or is longer than three + characters.</para> + + <para>Note that the character to use may be specified using + the <link linkend="MANGLINGCHAR"><parameter moreinfo="none">mangling char</parameter> + </link> option, if you don't like '~'.</para> + </listitem> + + <listitem> + <para>The first three alphanumeric characters of the final + extension are preserved, forced to upper case and appear as the + extension of the mangled name. The final extension is defined as that + part of the original filename after the rightmost dot. If there are no + dots in the filename, the mangled name will have no extension (except + in the case of "hidden files" - see below).</para> + </listitem> + + <listitem> + <para>Files whose UNIX name begins with a dot will be + presented as DOS hidden files. The mangled name will be created as + for other filenames, but with the leading dot removed and "___" as + its extension regardless of actual original extension (that's three + underscores).</para> + </listitem> + </itemizedlist> + + <para>The two-digit hash value consists of upper case alphanumeric characters.</para> + + <para>This algorithm can cause name collisions only if files + in a directory share the same first five alphanumeric characters. + The probability of such a clash is 1/1300.</para> + + <para>The name mangling (if enabled) allows a file to be + copied between UNIX directories from Windows/DOS while retaining + the long UNIX filename. UNIX files can be renamed to a new extension + from Windows/DOS and will retain the same basename. Mangled names + do not change between sessions.</para> +</description> +<value type="default">yes</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/mangleprefix.xml b/docs/smbdotconf/filename/mangleprefix.xml new file mode 100644 index 0000000000..a8c7f8e1bc --- /dev/null +++ b/docs/smbdotconf/filename/mangleprefix.xml @@ -0,0 +1,19 @@ +<samba:parameter name="mangle prefix" + context="G" + type="string" + advanced="1" developer="1" + xmlns:samba="http://samba.org/common"> +<description> + <para> controls the number of prefix + characters from the original name used when generating + the mangled names. A larger value will give a weaker + hash and therefore more name collisions. The minimum + value is 1 and the maximum value is 6.</para> + + <para> + mangle prefix is effective only when mangling method is hash2. + </para> +</description> +<value type="default">1</value> +<value type="example">4</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/manglingchar.xml b/docs/smbdotconf/filename/manglingchar.xml new file mode 100644 index 0000000000..9586e96db2 --- /dev/null +++ b/docs/smbdotconf/filename/manglingchar.xml @@ -0,0 +1,13 @@ +<samba:parameter name="mangling char" + context="S" + type="string" + xmlns:samba="http://samba.org/common"> + <description> + <para>This controls what character is used as + the <emphasis>magic</emphasis> character in <link linkend="NAMEMANGLINGSECT">name mangling</link>. The + default is a '~' but this may interfere with some software. Use this option to set + it to whatever you prefer. This is effective only when mangling method is hash.</para> +</description> +<value type="default">~</value> +<value type="example">^</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/manglingmethod.xml b/docs/smbdotconf/filename/manglingmethod.xml new file mode 100644 index 0000000000..b23ad23f7d --- /dev/null +++ b/docs/smbdotconf/filename/manglingmethod.xml @@ -0,0 +1,18 @@ +<samba:parameter name="mangling method" + context="G" + type="string" + advanced="1" developer="1" + xmlns:samba="http://samba.org/common"> +<description> + <para> controls the algorithm used for the generating + the mangled names. Can take two different values, "hash" and + "hash2". "hash" is the default and is the algorithm that has been + used in Samba for many years. "hash2" is a newer and considered + a better algorithm (generates less collisions) in the names. + However, many Win32 applications store the mangled names and so + changing to the new algorithm must not be done + lightly as these applications may break unless reinstalled.</para> +</description> +<value type="default">hash2</value> +<value type="example">hash</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/maparchive.xml b/docs/smbdotconf/filename/maparchive.xml new file mode 100644 index 0000000000..ff117c83ea --- /dev/null +++ b/docs/smbdotconf/filename/maparchive.xml @@ -0,0 +1,20 @@ +<samba:parameter name="map archive" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This controls whether the DOS archive attribute + should be mapped to the UNIX owner execute bit. The DOS archive bit + is set when a file has been modified since its last backup. One + motivation for this option it to keep Samba/your PC from making + any file it touches from becoming executable under UNIX. This can + be quite annoying for shared source code, documents, etc...</para> + + <para>Note that this requires the <parameter moreinfo="none">create mask</parameter> + parameter to be set such that owner execute bit is not masked out + (i.e. it must include 100). See the parameter <link linkend="CREATEMASK"> + <parameter moreinfo="none">create mask</parameter></link> for details.</para> +</description> + +<value type="default">yes</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/maphidden.xml b/docs/smbdotconf/filename/maphidden.xml new file mode 100644 index 0000000000..2b84d2afb9 --- /dev/null +++ b/docs/smbdotconf/filename/maphidden.xml @@ -0,0 +1,16 @@ +<samba:parameter name="map hidden" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This controls whether DOS style hidden files + should be mapped to the UNIX world execute bit.</para> + + <para>Note that this requires the <parameter moreinfo="none">create mask</parameter> + to be set such that the world execute bit is not masked out (i.e. + it must include 001). See the parameter <link linkend="CREATEMASK"> + <parameter moreinfo="none">create mask</parameter></link> for details.</para> + +</description> +<value type="boolean">no</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/mapsystem.xml b/docs/smbdotconf/filename/mapsystem.xml new file mode 100644 index 0000000000..9788f99370 --- /dev/null +++ b/docs/smbdotconf/filename/mapsystem.xml @@ -0,0 +1,15 @@ +<samba:parameter name="map system" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This controls whether DOS style system files + should be mapped to the UNIX group execute bit.</para> + + <para>Note that this requires the <parameter moreinfo="none">create mask</parameter> + to be set such that the group execute bit is not masked out (i.e. + it must include 010). See the parameter <link linkend="CREATEMASK"> + <parameter moreinfo="none">create mask</parameter></link> for details.</para> + </description> + <value type="default">no</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/preservecase.xml b/docs/smbdotconf/filename/preservecase.xml new file mode 100644 index 0000000000..a6e05bcfb9 --- /dev/null +++ b/docs/smbdotconf/filename/preservecase.xml @@ -0,0 +1,14 @@ +<samba:parameter name="preserve case" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para> This controls if new filenames are created + with the case that the client passes, or if they are forced to + be the <link linkend="DEFAULTCASE"><parameter moreinfo="none">default case + </parameter></link>.</para> + <para>See the section on <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link> for a fuller discussion.</para> +</description> + +<value type="default">yes</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/shortpreservecase.xml b/docs/smbdotconf/filename/shortpreservecase.xml new file mode 100644 index 0000000000..ca86ae07a8 --- /dev/null +++ b/docs/smbdotconf/filename/shortpreservecase.xml @@ -0,0 +1,17 @@ +<samba:parameter name="short preserve case" + context="S" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This boolean parameter controls if new files + which conform to 8.3 syntax, that is all in upper case and of + suitable length, are created upper case, or if they are forced + to be the <link linkend="DEFAULTCASE"><parameter moreinfo="none">default case + </parameter></link>. This option can be use with <link linkend="PRESERVECASE"><command moreinfo="none">preserve case = yes</command> + </link> to permit long filenames to retain their case, while short + names are lowered. </para> + + <para>See the section on <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link>.</para> +</description> +<value type="default">yes</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/statcache.xml b/docs/smbdotconf/filename/statcache.xml new file mode 100644 index 0000000000..4f160779cc --- /dev/null +++ b/docs/smbdotconf/filename/statcache.xml @@ -0,0 +1,13 @@ +<samba:parameter name="stat cache" + context="G" + developer="1" + type="boolean" + xmlns:samba="http://samba.org/common"> +<description> + <para>This parameter determines if <citerefentry><refentrytitle>smbd</refentrytitle> + <manvolnum>8</manvolnum></citerefentry> will use a cache in order to + speed up case insensitive name mappings. You should never need + to change this parameter.</para> +</description> +<value type="default">yes</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/vetofiles.xml b/docs/smbdotconf/filename/vetofiles.xml new file mode 100644 index 0000000000..495722d295 --- /dev/null +++ b/docs/smbdotconf/filename/vetofiles.xml @@ -0,0 +1,46 @@ +<samba:parameter name="veto files" + context="S" + type="string" + xmlns:samba="http://samba.org/common"> + <description> + <para>This is a list of files and directories that + are neither visible nor accessible. Each entry in the list must + be separated by a '/', which allows spaces to be included + in the entry. '*' and '?' can be used to specify multiple files + or directories as in DOS wildcards.</para> + + <para>Each entry must be a unix path, not a DOS path and + must <emphasis>not</emphasis> include the unix directory + separator '/'.</para> + + <para>Note that the <parameter moreinfo="none">case sensitive</parameter> option + is applicable in vetoing files.</para> + + <para>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 <emphasis>fail</emphasis> unless you also set + the <parameter moreinfo="none">delete veto files</parameter> parameter to + <parameter moreinfo="none">yes</parameter>.</para> + + <para>Setting this parameter will affect the performance + of Samba, as it will be forced to check all files and directories + for a match as they are scanned.</para> +</description> +<related>hide files</related> +<related>case sensitive</related> + +<value type="default"><comment>No files or directories are vetoed.</comment></value> + +<value type="example"> +; Veto any files containing the word Security, +; any ending in .tmp, and any directory containing the +; word root. +veto files = /*Security*/*.tmp/*root*/ + +; Veto the Apple specific files that a NetAtalk server +; creates. +veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ +</value> +</samba:parameter> diff --git a/docs/smbdotconf/filename/vetooplockfiles.xml b/docs/smbdotconf/filename/vetooplockfiles.xml new file mode 100644 index 0000000000..6f546ecc16 --- /dev/null +++ b/docs/smbdotconf/filename/vetooplockfiles.xml @@ -0,0 +1,25 @@ +<samba:parameter name="veto oplock files" + context="S" + type="string" + xmlns:samba="http://samba.org/common"> + <description> + <para>This parameter is only valid when the <link linkend="OPLOCKS"> + <parameter moreinfo="none">oplocks</parameter></link> + parameter is turned on for a share. It allows the Samba administrator + to selectively turn off the granting of oplocks on selected files that + match a wildcarded list, similar to the wildcarded list used in the + <link linkend="VETOFILES"><parameter moreinfo="none">veto files</parameter></link> + parameter.</para> + + + <para>You might want to do this on files that you know will + be heavily contended for by clients. A good example of this + is in the NetBench SMB benchmark program, which causes heavy + client contention for files ending in <filename moreinfo="none">.SEM</filename>. + To cause Samba not to grant oplocks on these files you would use + the line (either in the [global] section or in the section for + the particular NetBench share :</para> +</description> +<value type="default"><comment>No files are vetoed for oplock grants</comment></value> +<value type="example">/.*SEM/</value> +</samba:parameter> |