- Timestamp:
- Nov 12, 2012, 5:38:52 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.5.x/docs/htmldocs/manpages/mount.cifs.8.html
r599 r736 61 61 at version 1.10 or higher to support specifying the uid in non-numeric 62 62 form. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more 63 information. </p></dd><dt><span class="term">forceuid</span></dt><dd><p>instructs the client to ignore any uid provided by 63 information. </p></dd><dt><span class="term">prefixpath=<em class="replaceable"><code>arg</code></em></span></dt><dd><p> 64 It's possible to mount a subdirectory of a share. The preferred way 65 to do this is to append the path to the UNC when mounting. However, 66 it's also possible to do the same by setting this option and 67 providing the path there. 68 </p></dd><dt><span class="term">cifsacl</span></dt><dd><p> 69 This option is used to map CIFS/NTFS ACLs to/from Linux permission 70 bits, map SIDs to/from UIDs and GIDs, and get and set Security 71 Descriptors. 72 </p></dd><dt><span class="term">forceuid</span></dt><dd><p>instructs the client to ignore any uid provided by 64 73 the server for files and directories and to always assign the owner to 65 74 be the value of the uid= option. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more information.</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 or … … 75 84 if it is not specified, the default ports will be tried i.e. 76 85 port 445 is tried and if no response then port 139 is tried. 77 </p></dd><dt><span class="term">servern =<em class="replaceable"><code>arg</code></em></span></dt><dd><p>86 </p></dd><dt><span class="term">servernetbiosname=<em class="replaceable"><code>arg</code></em></span></dt><dd><p> 78 87 Specify the server netbios name (RFC1001 name) to use 79 88 when attempting to setup a session to the server. Although … … 84 93 support a default server name. A server name can be up 85 94 to 15 characters long and is usually uppercased. 86 </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 RFC100195 </p></dd><dt><span class="term">servern=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>synonym for <span class="emphasis"><em>servernetbiosname=</em></span></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 87 96 source name to use to represent the client netbios machine 88 97 name when doing the RFC1001 netbios session initialize. … … 154 163 "noacl" on mount.</p></dd><dt><span class="term">nocase</span></dt><dd><p>Request case insensitive path name matching (case 155 164 sensitive is the default if the server suports it). 165 </p></dd><dt><span class="term">ignorecase</span></dt><dd><p> 166 Synonym for <span class="emphasis"><em>nocase</em></span> 156 167 </p></dd><dt><span class="term">sec=</span></dt><dd><p>Security mode. Allowed values are:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>none attempt to connection as a null user (no name) </p></li><li class="listitem"><p>krb5 Use Kerberos version 5 authentication</p></li><li class="listitem"><p>krb5i Use Kerberos authentication and packet signing</p></li><li class="listitem"><p>ntlm Use NTLM password hashing (default)</p></li><li class="listitem"><p>ntlmi Use NTLM password hashing with signing (if 157 168 /proc/fs/cifs/PacketSigningEnabled on or if … … 220 231 </p></dd><dt><span class="term">wsize=<em class="replaceable"><code>arg</code></em></span></dt><dd><p>default network write size (default 57344) 221 232 maximum wsize currently allowed by CIFS is 57344 (fourteen 222 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" title="SERVICE FORMATTING AND DELIMITERS"><a name="id307577"></a><h2>SERVICE FORMATTING AND DELIMITERS</h2><p> 233 4096 byte pages)</p></dd><dt><span class="term">noposixpaths</span></dt><dd><p> 234 If unix extensions are enabled on a share, then the client will 235 typically allow filenames to include any character besides '/' in a 236 pathname component, and will use forward slashes as a pathname 237 delimiter. This option prevents the client from attempting to 238 negotiate the use of posix-style pathnames to the server. 239 </p></dd><dt><span class="term">posixpaths</span></dt><dd><p> 240 Inverse of <span class="emphasis"><em>noposixpaths</em></span> 241 </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" title="SERVICE FORMATTING AND DELIMITERS"><a name="id307612"></a><h2>SERVICE FORMATTING AND DELIMITERS</h2><p> 223 242 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. 224 243 </p><p> 225 244 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. 226 </p></div><div class="refsect1" title="INODE NUMBERS"><a name="id307 595"></a><h2>INODE NUMBERS</h2><p>245 </p></div><div class="refsect1" title="INODE NUMBERS"><a name="id307630"></a><h2>INODE NUMBERS</h2><p> 227 246 When Unix Extensions are enabled, we use the actual inode 228 247 number provided by the server in response to the POSIX calls as an … … 244 263 numbers smaller than 2 power 32 on the client. But you may not be able 245 264 to detect hardlinks properly. 246 </p></div><div class="refsect1" title="FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS"><a name="id3076 20"></a><h2>FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS</h2><p> The core CIFS protocol does not provide unix ownership265 </p></div><div class="refsect1" title="FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS"><a name="id307655"></a><h2>FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS</h2><p> The core CIFS protocol does not provide unix ownership 247 266 information or mode for files and directories. Because of this, files 248 267 and directories will generally appear to be owned by whatever values the … … 269 288 altogether via the noperm option. Server-side permission checks cannot be 270 289 overriden. The permission checks done by the server will always correspond to 271 the credentials used to mount the share, and not necessarily to the user who is accessing the share.</p></div><div class="refsect1" title="ENVIRONMENT VARIABLES"><a name="id3076 58"></a><h2>ENVIRONMENT VARIABLES</h2><p>290 the credentials used to mount the share, and not necessarily to the user who is accessing the share.</p></div><div class="refsect1" title="ENVIRONMENT VARIABLES"><a name="id307697"></a><h2>ENVIRONMENT VARIABLES</h2><p> 272 291 The variable <span class="emphasis"><em>USER</em></span> may contain the username of the 273 292 person to be used to authenticate to the server. … … 281 300 of a file to read the password from. A single line of input is 282 301 read and used as the password. 283 </p></div><div class="refsect1" title="NOTES"><a name="id307 687"></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. When installed as a setuid program, the program follows the conventions set forth by the mount program for user mounts.</p><p>302 </p></div><div class="refsect1" title="NOTES"><a name="id307726"></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. When installed as a setuid program, the program follows the conventions set forth by the mount program for user mounts.</p><p> 284 303 Some samba client tools like smbclient(8) honour client-side 285 304 configuration parameters present in smb.conf. Unlike those 286 305 client tools, <span class="emphasis"><em>mount.cifs</em></span> ignores smb.conf 287 306 completely. 288 </p></div><div class="refsect1" title="CONFIGURATION"><a name="id3077 06"></a><h2>CONFIGURATION</h2><p>307 </p></div><div class="refsect1" title="CONFIGURATION"><a name="id307745"></a><h2>CONFIGURATION</h2><p> 289 308 The primary mechanism for making configuration changes and for reading 290 309 debug information for the cifs vfs is via the Linux /proc filesystem. … … 297 316 installation (device driver load). 298 317 For more information see the kernel file <code class="filename">fs/cifs/README</code>. 299 </p></div><div class="refsect1" title="BUGS"><a name="id3077 32"></a><h2>BUGS</h2><p>Mounting using the CIFS URL specification is currently not supported.318 </p></div><div class="refsect1" title="BUGS"><a name="id307771"></a><h2>BUGS</h2><p>Mounting using the CIFS URL specification is currently not supported. 300 319 </p><p>The credentials file does not handle usernames or passwords with 301 320 leading space.</p><p> … … 305 324 when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and 306 325 server type you are trying to contact. 307 </p></div><div class="refsect1" title="VERSION"><a name="id3077 51"></a><h2>VERSION</h2><p>This man page is correct for version 1.52 of308 the cifs vfs filesystem (roughly Linux kernel 2.6.24).</p></div><div class="refsect1" title="SEE ALSO"><a name="id307 761"></a><h2>SEE ALSO</h2><p>326 </p></div><div class="refsect1" title="VERSION"><a name="id307790"></a><h2>VERSION</h2><p>This man page is correct for version 1.52 of 327 the cifs vfs filesystem (roughly Linux kernel 2.6.24).</p></div><div class="refsect1" title="SEE ALSO"><a name="id307801"></a><h2>SEE ALSO</h2><p> 309 328 Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel 310 329 source tree may contain additional options and information. 311 </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" title="AUTHOR"><a name="id307 781"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax and manpage were loosely based on that of smbmount. It330 </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" title="AUTHOR"><a name="id307820"></a><h2>AUTHOR</h2><p>Steve French</p><p>The syntax and manpage were loosely based on that of smbmount. It 312 331 was converted to Docbook/XML by Jelmer Vernooij.</p><p>The maintainer of the Linux cifs vfs and the userspace 313 332 tool <span class="emphasis"><em>mount.cifs</em></span> is <a class="ulink" href="mailto:sfrench@samba.org" target="_top">Steve French</a>.
Note:
See TracChangeset
for help on using the changeset viewer.