Ignore:
Timestamp:
May 23, 2008, 6:56:41 AM (17 years ago)
Author:
Paul Smedley
Message:

Update source to 3.0.29

File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/samba-3.0/docs/htmldocs/manpages/mount.cifs.8.html

    r44 r134  
    1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>mount.cifs</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="mount.cifs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>mount.cifs &#8212; mount using the Common Internet File System (CIFS)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">mount.cifs</code> {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><a name="id259314"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>mount.cifs mounts a Linux CIFS filesystem. It
     1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>mount.cifs</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="mount.cifs.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>mount.cifs &#8212; mount using the Common Internet File System (CIFS)</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">mount.cifs</code> {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><a name="id283752"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p>mount.cifs mounts a Linux CIFS filesystem. It
    22is usually invoked indirectly by
    3 the <a href="mount.8.html"><span class="citerefentry"><span class="refentrytitle">mount</span>(8)</span></a> command when using the
     3the <a class="citerefentry" href="mount.8.html"><span class="citerefentry"><span class="refentrytitle">mount</span>(8)</span></a> command when using the
    44"-t cifs" option. This command only works in Linux, and the kernel must
    55support the cifs filesystem. The CIFS protocol is the successor to the
    … …  
    2121        </p><p><span class="emphasis"><em>mount.cifs</em></span> causes the cifs vfs to launch a thread named cifsd. After mounting it keeps running until
    2222                the mounted resource is unmounted (usually via the umount utility).
    23         </p></div><div class="refsect1" lang="en"><a name="id259585"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">user=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>specifies the username to connect as. If
     23        </p></div><div class="refsect1" lang="en"><a name="id282767"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">user=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>specifies the username to connect as. If
    2424                                this is not given, then the environment variable <span class="emphasis"><em>USER</em></span> is used. This option can also take the
    2525form "user%password" or "workgroup/user" or
    … …  
    3131option is not given then the environment variable
    3232<span class="emphasis"><em>PASSWD</em></span> is used. If the password is not specified
    33 directly or indirectly via an argument to mount <span class="emphasis"><em>mount.cifs</em></span> will prompt
     33directly or indirectly via an argument to mount, <span class="emphasis"><em>mount.cifs</em></span> will prompt
    3434for a password, unless the guest option is specified.
    3535</p><p>Note that a password which contains the delimiter
    … …  
    5151        the mounted filesystem.
    5252        It may be specified as either a username or a numeric uid.
    53         This parameter is ignored when the target server supports
    54         the CIFS Unix extensions.</p></dd><dt><span class="term">gid=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the gid that will own all files on
    55 the mounted filesystem.
    56 It may be specified as either a groupname or a numeric
    57 gid. This parameter is ignored when the target server supports
    58 the CIFS Unix extensions.
     53        For mounts to servers which do support the CIFS Unix extensions,
     54        such as a properly configured Samba server, the server provides
     55                the uid, gid and mode so this parameter should not be
     56                specified unless the server and client uid and gid
     57                numbering differ.  If the server and client are in the
     58                same domain (e.g. running winbind or nss_ldap) and
     59                the server supports the Unix Extensions then the uid
     60                and gid can be retrieved from the server (and uid
     61                and gid would not have to be specifed on the mount.
     62                For servers which do not support the CIFS Unix
     63                extensions, the default uid (and gid) returned on lookup
     64                of existing files will be the uid (gid) of the person
     65                who executed the mount (root, except when mount.cifs
     66                is configured setuid for user mounts) unless the "uid="
     67                (gid) mount option is specified.  For the uid (gid) of newly
     68                created files and directories, ie files created since
     69                the last mount of the server share, the expected uid
     70                (gid) is cached as long as the inode remains in
     71                memory on the client.   Also note that permission
     72                checks (authorization checks) on accesses to a file occur
     73                at the server, but there are cases in which an administrator
     74                may want to restrict at the client as well.  For those
     75                servers which do not report a uid/gid owner
     76                (such as Windows), permissions can also be checked at the
     77                client, and a crude form of client side permission checking
     78                can be enabled by specifying file_mode and dir_mode on
     79                the client.  Note that the mount.cifs helper must be
     80                at version 1.10 or higher to support specifying the uid
     81                (or gid) in non-numeric form.
     82        </p></dd><dt><span class="term">gid=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the gid that will own all files on
     83the mounted filesystem.  It may be specified as either a groupname or a numeric
     84gid. For other considerations see the description of uid above.
    5985                </p></dd><dt><span class="term">port=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the port number on the server to attempt to contact to negotiate
    6086CIFS support.  If the CIFS server is not listening on this port or
    6187if it is not specified, the default ports will be tried i.e.
    6288port 445 is tried and if no response then port 139 is tried.
    63                 </p></dd><dt><span class="term">netbiosname=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>When mounting to servers via port 139, specifies the RFC1001
     89                </p></dd><dt><span class="term">servern=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>
     90                Specify the server netbios name (RFC1001 name) to use
     91                when attempting to setup a session to the server. Although
     92                rarely needed for mounting to newer servers, this option
     93                is needed for mounting to some older servers (such
     94                as OS/2 or Windows 98 and Windows ME) since when connecting
     95                over port 139 they, unlike most newer servers, do not
     96                support a default server name.  A server name can be up
     97                to 15 characters long and is usually uppercased.
     98                </p></dd><dt><span class="term">netbiosname=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>When mounting to servers via port 139, specifies the RFC1001
    6499                source name to use to represent the client netbios machine
    65100                name when doing the RFC1001 netbios session initialize.
    66101                </p></dd><dt><span class="term">file_mode=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>If the server does not support the CIFS Unix extensions this
    67102                                overrides the default file mode.</p></dd><dt><span class="term">dir_mode=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>If the server does not support the CIFS Unix extensions this
    68                                 overrides the default mode for directories. </p></dd><dt><span class="term">ip=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the destination host or IP address.</p></dd><dt><span class="term">domain=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the domain (workgroup) of the user </p></dd><dt><span class="term">guest</span></dt><dd><p>don't prompt for a password </p></dd><dt><span class="term">iocharset</span></dt><dd><p>Charset used to convert local path names to and from
     103                                overrides the default mode for directories. </p></dd><dt><span class="term">ip=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the destination IP address.  This option is set automatically if the server name portion of the requested UNC name can be resolved so rarely needs to be specified by the user.</p></dd><dt><span class="term">domain=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>sets the domain (workgroup) of the user </p></dd><dt><span class="term">guest</span></dt><dd><p>don't prompt for a password </p></dd><dt><span class="term">iocharset</span></dt><dd><p>Charset used to convert local path names to and from
    69104                Unicode. Unicode is used by default for network path
    70105                names if the server supports it. If iocharset is
    … …  
    164199                </p></dd><dt><span class="term">noserverino</span></dt><dd><p>client generates inode numbers (rather than using the actual one
    165200                from the server) by default.
    166                 </p></dd><dt><span class="term">nouser_xattr</span></dt><dd><p>(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. </p></dd><dt><span class="term">rsize=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>default network read size</p></dd><dt><span class="term">wsize=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>default network write size</p></dd><dt><span class="term">--verbose</span></dt><dd><p>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</p><p>mount -t cifs //server/share /mnt --verbose -o user=username</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id300777"></a><h2>ENVIRONMENT VARIABLES</h2><p>
     201                </p></dd><dt><span class="term">nouser_xattr</span></dt><dd><p>(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. </p></dd><dt><span class="term">rsize=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>default network read size (usually 16K). The client currently
     202                can not use rsize larger than CIFSMaxBufSize. CIFSMaxBufSize
     203                defaults to 16K and may be changed (from 8K to the maximum
     204                kmalloc size allowed by your kernel) at module install time
     205                for cifs.ko. Setting CIFSMaxBufSize to a very large value
     206                will cause cifs to use more memory and may reduce performance
     207                in some cases.  To use rsize greater than 127K (the original
     208                cifs protocol maximum) also requires that the server support
     209                a new Unix Capability flag (for very large read) which some
     210                newer servers (e.g. Samba 3.0.26 or later) do. rsize can be
     211                set from a minimum of 2048 to a maximum of 130048 (127K or
     212                CIFSMaxBufSize, whichever is smaller)
     213
     214                </p></dd><dt><span class="term">wsize=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>default network write size (default 57344)
     215                maximum wsize currently allowed by CIFS is 57344 (fourteen
     216                4096 byte pages)</p></dd><dt><span class="term">--verbose</span></dt><dd><p>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</p><p>mount -t cifs //server/share /mnt --verbose -o user=username</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id324899"></a><h2>SERVICE FORMATTING AND DELIMITERS</h2><p>
     217                It's generally preferred to use forward slashes (/) as a delimiter in service names. They are considered to be the "universal delimiter" since they are generally not allowed to be embedded within path components on Windows machines and the client can convert them to blackslashes (\) unconditionally. Conversely, backslash characters are allowed by POSIX to be part of a path component, and can't be automatically converted in the same way.
     218        </p><p>
     219                mount.cifs will attempt to convert backslashes to forward slashes where it's able to do so, but it cannot do so in any path component following the sharename.
     220        </p></div><div class="refsect1" lang="en"><a name="id324918"></a><h2>ENVIRONMENT VARIABLES</h2><p>
    167221                The variable <span class="emphasis"><em>USER</em></span> may contain the username of the
    168222person to be used to authenticate to the server.
    … …  
    176230of a file to read the password from. A single line of input is
    177231read and used as the password.
    178         </p></div><div class="refsect1" lang="en"><a name="id300809"></a><h2>NOTES</h2><p>This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.</p></div><div class="refsect1" lang="en"><a name="id300820"></a><h2>CONFIGURATION</h2><p>
     232        </p></div><div class="refsect1" lang="en"><a name="id324946"></a><h2>NOTES</h2><p>This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.</p></div><div class="refsect1" lang="en"><a name="id324957"></a><h2>CONFIGURATION</h2><p>
    179233The primary mechanism for making configuration changes and for reading
    180234debug information for the cifs vfs is via the Linux /proc filesystem.
    … …  
    187241installation (device driver load).
    188242For more information see the kernel file <code class="filename">fs/cifs/README</code>.
    189 </p></div><div class="refsect1" lang="en"><a name="id300847"></a><h2>BUGS</h2><p>Mounting using the CIFS URL specification is currently not supported.
     243</p></div><div class="refsect1" lang="en"><a name="id324982"></a><h2>BUGS</h2><p>Mounting using the CIFS URL specification is currently not supported.
    190244        </p><p>The credentials file does not handle usernames or passwords with
    191245                leading space.</p><p>
    … …  
    195249when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and
    196250server type you are trying to contact.
    197 </p></div><div class="refsect1" lang="en"><a name="id300867"></a><h2>VERSION</h2><p>This man page is correct for version 1.39 of
    198         the cifs vfs filesystem (roughly Linux kernel 2.6.15).</p></div><div class="refsect1" lang="en"><a name="id300878"></a><h2>SEE ALSO</h2><p>
     251</p></div><div class="refsect1" lang="en"><a name="id325003"></a><h2>VERSION</h2><p>This man page is correct for version 1.52 of
     252        the cifs vfs filesystem (roughly Linux kernel 2.6.24).</p></div><div class="refsect1" lang="en"><a name="id325013"></a><h2>SEE ALSO</h2><p>
    199253        Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel
    200254        source tree may contain additional options and information.
    201 </p><p><a href="umount.cifs.8.html"><span class="citerefentry"><span class="refentrytitle">umount.cifs</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id300898"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax and manpage were loosely based on that of smbmount. It
     255</p><p><a class="citerefentry" href="umount.cifs.8.html"><span class="citerefentry"><span class="refentrytitle">umount.cifs</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id325033"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax and manpage were loosely based on that of smbmount. It
    202256                was converted to Docbook/XML by Jelmer Vernooij.</p><p>The maintainer of the Linux cifs vfs and the userspace
    203                 tool <span class="emphasis"><em>mount.cifs</em></span> is <a href="mailto:sfrench@samba.org" target="_top">Steve French</a>.
    204                 The <a href="mailto:linux-cifs-client@lists.samba.org" target="_top">Linux CIFS Mailing list</a>
     257                tool <span class="emphasis"><em>mount.cifs</em></span> is <a class="ulink" href="mailto:sfrench@samba.org" target="_top">Steve French</a>.
     258                The <a class="ulink" href="mailto:linux-cifs-client@lists.samba.org" target="_top">Linux CIFS Mailing list</a>
    205259                is the preferred place to ask questions regarding these programs.
    206260        </p></div></div></body></html>
Note: See TracChangeset for help on using the changeset viewer.