1<?xml version="1.0" encoding="iso-8859-1"?> 2<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc"> 3<refentry id="mount.cifs.8"> 4 5<refmeta> 6 <refentrytitle>mount.cifs</refentrytitle> 7 <manvolnum>8</manvolnum> 8 <refmiscinfo class="source">Samba</refmiscinfo> 9 <refmiscinfo class="manual">System Administration tools</refmiscinfo> 10 <refmiscinfo class="version">3.5</refmiscinfo> 11</refmeta> 12 13 14<refnamediv> 15 <refname>mount.cifs</refname> 16 <refpurpose>mount using the Common Internet File System (CIFS)</refpurpose> 17</refnamediv> 18 19<refsynopsisdiv> 20 <cmdsynopsis> 21 22 <command>mount.cifs</command> 23 <arg choice="req">service</arg> 24 <arg choice="req">mount-point</arg> 25 <arg choice="opt">-o options</arg> 26 </cmdsynopsis> 27</refsynopsisdiv> 28 29<refsect1> 30 <title>DESCRIPTION</title> 31 32 <para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle> 33 <manvolnum>7</manvolnum></citerefentry> suite.</para> 34 35 <para>mount.cifs mounts a Linux CIFS filesystem. It 36is usually invoked indirectly by 37the <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> command when using the 38"-t cifs" option. This command only works in Linux, and the kernel must 39support the cifs filesystem. The CIFS protocol is the successor to the 40SMB protocol and is supported by most Windows servers and many other 41commercial servers and Network Attached Storage appliances as well as 42by the popular Open Source server Samba. 43 </para> 44 45 <para> 46 The mount.cifs utility attaches the UNC name (exported network resource) 47 specified as <emphasis>service</emphasis> (using //server/share syntax, 48 where "server" is the server name or IP address and "share" is the name 49 of the share) to the local directory <emphasis>mount-point</emphasis>. 50 </para> 51 52 <para> 53 Options to <emphasis>mount.cifs</emphasis> are specified as a comma-separated 54list of key=value pairs. It is possible to send options other 55than those listed here, assuming that the cifs filesystem kernel module (cifs.ko) supports them. 56Unrecognized cifs mount options passed to the cifs vfs kernel code will be logged to the 57kernel log. 58 59 </para> 60 61 <para><emphasis>mount.cifs</emphasis> causes the cifs vfs to launch a thread named cifsd. After mounting it keeps running until 62 the mounted resource is unmounted (usually via the umount utility). 63 </para> 64 65 <para> 66 <emphasis>mount.cifs -V</emphasis> command displays the version of cifs mount helper. 67 </para> 68 <para> 69 70 <emphasis>modinfo cifs</emphasis> command displays the version of cifs module. 71 </para> 72 73</refsect1> 74 75<refsect1> 76 <title>OPTIONS</title> 77 <variablelist> 78 <varlistentry><term>user=<replaceable>arg</replaceable></term> 79 80 <listitem><para>specifies the username to connect as. If 81 this is not given, then the environment variable <emphasis>USER</emphasis> is used. This option can also take the 82form "user%password" or "workgroup/user" or 83"workgroup/user%password" to allow the password and workgroup 84to be specified as part of the username. 85 </para> 86 87<note> 88 <para> 89 The cifs vfs accepts the parameter <parameter>user=</parameter>, or for users familiar with smbfs it accepts the longer form of the parameter <parameter>username=</parameter>. Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters <parameter>pass=</parameter>,<parameter>dom=</parameter> and <parameter>cred=</parameter>. 90 </para> 91</note> 92 93 </listitem> 94 </varlistentry> 95 96 <varlistentry><term>password=<replaceable>arg</replaceable></term> 97 98 <listitem><para>specifies the CIFS password. If this 99option is not given then the environment variable 100<emphasis>PASSWD</emphasis> is used. If the password is not specified 101directly or indirectly via an argument to mount, <emphasis>mount.cifs</emphasis> will prompt 102for a password, unless the guest option is specified. 103</para> 104 105<para>Note that a password which contains the delimiter 106character (i.e. a comma ',') will fail to be parsed correctly 107on the command line. However, the same password defined 108in the PASSWD environment variable or via a credentials file (see 109below) or entered at the password prompt will be read correctly. 110</para> 111 </listitem></varlistentry> 112 113 <varlistentry><term>credentials=<replaceable>filename</replaceable></term> 114 115 <listitem><para> 116 specifies a file that contains a username 117 and/or password and optionally the name of the 118 workgroup. The format of the file is: 119 </para> 120 121<programlisting> 122 username=<replaceable>value</replaceable> 123 password=<replaceable>value</replaceable> 124 domain=<replaceable>value</replaceable> 125</programlisting> 126 127 <para> 128This is preferred over having passwords in plaintext in a 129shared file, such as <filename>/etc/fstab</filename>. Be sure to protect any 130credentials file properly. 131 </para> 132 </listitem></varlistentry> 133 134 <varlistentry> 135 <term>uid=<replaceable>arg</replaceable></term> 136 <listitem> 137 138 <para>sets the uid that will own all files or directories on the 139mounted filesystem when the server does not provide ownership 140information. It may be specified as either a username or a numeric uid. 141When not specified, the default is uid 0. The mount.cifs helper must be 142at version 1.10 or higher to support specifying the uid in non-numeric 143form. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more 144information. </para> 145 146</listitem> 147</varlistentry> 148 149<varlistentry> 150 <term>forceuid</term> 151 <listitem> 152 <para>instructs the client to ignore any uid provided by 153the server for files and directories and to always assign the owner to 154be the value of the uid= option. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more information.</para> 155 </listitem> 156</varlistentry> 157 158<varlistentry> 159 <term>gid=<replaceable>arg</replaceable></term> 160 <listitem> 161 162 <para>sets the gid that will own all files or 163directories on the mounted filesystem when the server does not provide 164ownership information. It may be specified as either a groupname or a 165numeric gid. When not specified, the default is gid 0. The mount.cifs 166helper must be at version 1.10 or higher to support specifying the gid 167in non-numeric form. See the section on FILE AND DIRECTORY OWNERSHIP AND 168PERMISSIONS below for more information.</para> 169 170 </listitem> 171</varlistentry> 172 173<varlistentry> 174 <term>forcegid</term> 175 <listitem> 176 <para>instructs the client to ignore any gid provided by 177the server for files and directories and to always assign the owner to 178be the value of the gid= option. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more information.</para> 179 </listitem> 180</varlistentry> 181 182<varlistentry> 183 <term>port=<replaceable>arg</replaceable></term> 184 185 <listitem><para>sets the port number on the server to attempt to contact to negotiate 186CIFS support. If the CIFS server is not listening on this port or 187if it is not specified, the default ports will be tried i.e. 188port 445 is tried and if no response then port 139 is tried. 189 </para></listitem> 190 </varlistentry> 191 192 <varlistentry> 193 <term>servern=<replaceable>arg</replaceable></term> 194 195 <listitem><para> 196 Specify the server netbios name (RFC1001 name) to use 197 when attempting to setup a session to the server. Although 198 rarely needed for mounting to newer servers, this option 199 is needed for mounting to some older servers (such 200 as OS/2 or Windows 98 and Windows ME) since when connecting 201 over port 139 they, unlike most newer servers, do not 202 support a default server name. A server name can be up 203 to 15 characters long and is usually uppercased. 204 </para></listitem> 205 </varlistentry> 206 207 <varlistentry> 208 <term>netbiosname=<replaceable>arg</replaceable></term> 209 210 <listitem><para>When mounting to servers via port 139, specifies the RFC1001 211 source name to use to represent the client netbios machine 212 name when doing the RFC1001 netbios session initialize. 213 </para></listitem> 214 </varlistentry> 215 216 <varlistentry> 217 <term>file_mode=<replaceable>arg</replaceable></term> 218 219 <listitem><para>If the server does not support the CIFS Unix extensions this 220 overrides the default file mode.</para></listitem> 221 </varlistentry> 222 223 <varlistentry> 224 <term>dir_mode=<replaceable>arg</replaceable></term> 225 226 <listitem><para>If the server does not support the CIFS Unix extensions this 227 overrides the default mode for directories. </para></listitem> 228 </varlistentry> 229 230 <varlistentry> 231 <term>ip=<replaceable>arg</replaceable></term> 232 233 <listitem><para>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.</para></listitem> 234 </varlistentry> 235 236 <varlistentry> 237 <term>domain=<replaceable>arg</replaceable></term> 238 239 <listitem><para>sets the domain (workgroup) of the user </para></listitem> 240 </varlistentry> 241 242 <varlistentry> 243 <term>guest</term> 244 245 <listitem><para>don't prompt for a password </para></listitem> 246 247 </varlistentry> 248 249 <varlistentry> 250 <term>iocharset</term> 251 252 <listitem><para>Charset used to convert local path names to and from 253 Unicode. Unicode is used by default for network path 254 names if the server supports it. If iocharset is 255 not specified then the nls_default specified 256 during the local client kernel build will be used. 257 If server does not support Unicode, this parameter is 258 unused. </para></listitem> 259 260 </varlistentry> 261 262 <varlistentry> 263 <term>ro</term> 264 265 <listitem><para>mount read-only</para></listitem> 266 267 </varlistentry> 268 269 <varlistentry> 270 <term>rw</term> 271 <listitem><para>mount read-write</para></listitem> 272 </varlistentry> 273 274 <varlistentry> 275 <term>setuids</term> 276 <listitem><para>If the CIFS Unix extensions are negotiated with the server 277 the client will attempt to set the effective uid and gid of 278 the local process on newly created files, directories, and 279 devices (create, mkdir, mknod). If the CIFS Unix Extensions 280 are not negotiated, for newly created files and directories 281 instead of using the default uid and gid specified on the 282 the mount, cache the new file's uid and gid locally which means 283 that the uid for the file can change when the inode is 284 reloaded (or the user remounts the share).</para></listitem> 285 </varlistentry> 286 287 <varlistentry> 288 <term>nosetuids</term> 289 <listitem><para>The client will not attempt to set the uid and gid on 290 on newly created files, directories, and devices (create, 291 mkdir, mknod) which will result in the server setting the 292 uid and gid to the default (usually the server uid of the 293 user who mounted the share). Letting the server (rather than 294 the client) set the uid and gid is the default.If the CIFS 295 Unix Extensions are not negotiated then the uid and gid for 296 new files will appear to be the uid (gid) of the mounter or the 297 uid (gid) parameter specified on the mount.</para></listitem> 298 </varlistentry> 299 300 <varlistentry> 301 <term>perm</term> 302 <listitem><para>Client does permission checks (vfs_permission check of uid 303 and gid of the file against the mode and desired operation), 304 Note that this is in addition to the normal ACL check on the 305 target machine done by the server software. 306 Client permission checking is enabled by default.</para></listitem> 307 </varlistentry> 308 309 <varlistentry> 310 <term>noperm</term> 311 <listitem><para>Client does not do permission checks. This can expose 312 files on this mount to access by other users on the local 313 client system. It is typically only needed when the server 314 supports the CIFS Unix Extensions but the UIDs/GIDs on the 315 client and server system do not match closely enough to allow 316 access by the user doing the mount. 317 Note that this does not affect the normal ACL check on the 318 target machine done by the server software (of the server 319 ACL against the user name provided at mount time).</para></listitem> 320 </varlistentry> 321 322 <varlistentry> 323 <term>dynperm</term> 324 <listitem><para>Instructs the server to maintain ownership and 325permissions in memory that can't be stored on the server. This information can disappear at any time (whenever the inode is flushed from the cache), so while this may help make some applications work, it's behavior is somewhat unreliable. See the section below on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS for more information. 326 </para></listitem> 327 </varlistentry> 328 329 <varlistentry> 330 <term>directio</term> 331 <listitem><para>Do not do inode data caching on files opened on this mount. 332 This precludes mmaping files on this mount. In some cases 333 with fast networks and little or no caching benefits on the 334 client (e.g. when the application is doing large sequential 335 reads bigger than page size without rereading the same data) 336 this can provide better performance than the default 337 behavior which caches reads (readahead) and writes 338 (writebehind) through the local Linux client pagecache 339 if oplock (caching token) is granted and held. Note that 340 direct allows write operations larger than page size 341 to be sent to the server. On some kernels this requires the cifs.ko module 342 to be built with the CIFS_EXPERIMENTAL configure option.</para></listitem> 343 </varlistentry> 344 345 <varlistentry> 346 <term>mapchars</term> 347 <listitem><para>Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters) 348 to the remap range (above 0xF000), which also 349 allows the CIFS client to recognize files created with 350 such characters by Windows's POSIX emulation. This can 351 also be useful when mounting to most versions of Samba 352 (which also forbids creating and opening files 353 whose names contain any of these seven characters). 354 This has no effect if the server does not support 355 Unicode on the wire. Please note that the files created 356 with mapchars mount option may not be accessible 357 if the share is mounted without that option.</para></listitem> 358 </varlistentry> 359 360 <varlistentry> 361 <term>nomapchars</term> 362 <listitem><para>Do not translate any of these seven characters (default)</para></listitem> 363 </varlistentry> 364 365 <varlistentry> 366 <term>intr</term> 367 <listitem><para>currently unimplemented</para></listitem> 368 </varlistentry> 369 370 <varlistentry> 371 <term>nointr</term> 372 <listitem><para>(default) currently unimplemented </para></listitem> 373 </varlistentry> 374 375 <varlistentry> 376 <term>hard</term> 377 <listitem><para>The program accessing a file on the cifs mounted file system will hang when the 378 server crashes.</para></listitem> 379 </varlistentry> 380 381 <varlistentry> 382 <term>soft</term> 383 <listitem><para>(default) The program accessing a file on the cifs mounted file system will not hang when the server crashes and will return errors to the user application.</para></listitem> 384 </varlistentry> 385 386 <varlistentry> 387 <term>noacl</term> 388 <listitem><para>Do not allow POSIX ACL operations even if server would support them.</para><para> 389 The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers 390 version 3.0.10 and later. Setting POSIX ACLs requires enabling both XATTR and 391 then POSIX support in the CIFS configuration options when building the cifs 392 module. POSIX ACL support can be disabled on a per mount basis by specifying 393 "noacl" on mount.</para> 394 </listitem> 395 </varlistentry> 396 397 <varlistentry> 398 <term>nocase</term> 399 <listitem> 400 <para>Request case insensitive path name matching (case 401 sensitive is the default if the server suports it). 402 </para> 403 </listitem> 404 </varlistentry> 405 406 <varlistentry> 407 <term>sec=</term> 408 <listitem> 409 <para>Security mode. Allowed values are:</para> 410 <itemizedlist> 411 <listitem><para>none attempt to connection as a null user (no name) </para></listitem> 412 <listitem><para>krb5 Use Kerberos version 5 authentication</para></listitem> 413 <listitem><para>krb5i Use Kerberos authentication and packet signing</para></listitem> 414 <listitem><para>ntlm Use NTLM password hashing (default)</para></listitem> 415 <listitem><para>ntlmi Use NTLM password hashing with signing (if 416 /proc/fs/cifs/PacketSigningEnabled on or if 417 server requires signing also can be the default)</para></listitem> 418 <listitem><para>ntlmv2 Use NTLMv2 password hashing</para></listitem> 419 <listitem><para>ntlmv2i Use NTLMv2 password hashing with packet signing</para></listitem> 420 </itemizedlist> 421 422 <para>[NB This [sec parameter] is under development and expected to be available in cifs kernel module 1.40 and later] 423 </para> 424 </listitem> 425 </varlistentry> 426 427 <varlistentry> 428 <term>nobrl</term> 429 <listitem> 430 <para>Do not send byte range lock requests to the server. 431 This is necessary for certain applications that break 432 with cifs style mandatory byte range locks (and most 433 cifs servers do not yet support requesting advisory 434 byte range locks). 435 </para> 436 </listitem> 437 </varlistentry> 438 439 <varlistentry> 440 <term>sfu</term> 441 <listitem> 442 <para> 443 When the CIFS Unix Extensions are not negotiated, attempt to 444 create device files and fifos in a format compatible with 445 Services for Unix (SFU). In addition retrieve bits 10-12 446 of the mode via the SETFILEBITS extended attribute (as 447 SFU does). In the future the bottom 9 bits of the mode 448 mode also will be emulated using queries of the security 449 descriptor (ACL). [NB: requires version 1.39 or later 450 of the CIFS VFS. To recognize symlinks and be able 451 to create symlinks in an SFU interoperable form 452 requires version 1.40 or later of the CIFS VFS kernel module. 453 </para> 454 </listitem> 455 </varlistentry> 456 457 <varlistentry> 458 <term>serverino</term> 459 <listitem><para>Use inode numbers (unique persistent file identifiers) 460 returned by the server instead of automatically generating 461 temporary inode numbers on the client. Although server inode numbers 462 make it easier to spot hardlinked files (as they will have 463 the same inode numbers) and inode numbers may be persistent (which is 464 userful for some sofware), 465 the server does not guarantee that the inode numbers 466 are unique if multiple server side mounts are exported under a 467 single share (since inode numbers on the servers might not 468 be unique if multiple filesystems are mounted under the same 469 shared higher level directory). Note that not all 470 servers support returning server inode numbers, although 471 those that support the CIFS Unix Extensions, and Windows 2000 and 472 later servers typically do support this (although not necessarily 473 on every local server filesystem). Parameter has no effect if 474 the server lacks support for returning inode numbers or equivalent. 475 </para></listitem> 476 </varlistentry> 477 478 <varlistentry> 479 <term>noserverino</term> 480 <listitem> 481 <para> 482 Client generates inode numbers (rather than 483 using the actual one from the server) by default. 484 </para> 485 <para> 486 See section <emphasis>INODE NUMBERS</emphasis> for 487 more information. 488 </para></listitem> 489 </varlistentry> 490 491 <varlistentry> 492 <term>nounix</term> 493 <listitem> 494 <para> 495 Disable the CIFS Unix Extensions for this mount. This 496 can be useful in order to turn off multiple settings at once. 497 This includes POSIX acls, POSIX locks, POSIX paths, symlink 498 support and retrieving uids/gids/mode from the server. This 499 can also be useful to work around a bug in a server that 500 supports Unix Extensions. 501 </para> 502 <para> 503 See section <emphasis>INODE NUMBERS</emphasis> for 504 more information. 505 </para> </listitem> 506 </varlistentry> 507 508 <varlistentry> 509 <term>nouser_xattr</term> 510 <listitem><para>(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. </para></listitem> 511 </varlistentry> 512 513 <varlistentry> 514 <term>rsize=<replaceable>arg</replaceable></term> 515 <listitem><para>default network read size (usually 16K). The client currently 516 can not use rsize larger than CIFSMaxBufSize. CIFSMaxBufSize 517 defaults to 16K and may be changed (from 8K to the maximum 518 kmalloc size allowed by your kernel) at module install time 519 for cifs.ko. Setting CIFSMaxBufSize to a very large value 520 will cause cifs to use more memory and may reduce performance 521 in some cases. To use rsize greater than 127K (the original 522 cifs protocol maximum) also requires that the server support 523 a new Unix Capability flag (for very large read) which some 524 newer servers (e.g. Samba 3.0.26 or later) do. rsize can be 525 set from a minimum of 2048 to a maximum of 130048 (127K or 526 CIFSMaxBufSize, whichever is smaller) 527 528 </para></listitem> 529 </varlistentry> 530 531 <varlistentry> 532 <term>wsize=<replaceable>arg</replaceable></term> 533 534 <listitem><para>default network write size (default 57344) 535 maximum wsize currently allowed by CIFS is 57344 (fourteen 536 4096 byte pages)</para></listitem> 537 </varlistentry> 538 <varlistentry> 539 <term>--verbose</term> 540 <listitem><para>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</para><para>mount -t cifs //server/share /mnt --verbose -o user=username</para></listitem> 541 </varlistentry> 542 543 544 </variablelist> 545</refsect1> 546 547<refsect1> 548 <title>SERVICE FORMATTING AND DELIMITERS</title> 549 550 <para> 551 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. 552 </para> 553 <para> 554 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. 555 </para> 556</refsect1> 557 558<refsect1> 559 <title>INODE NUMBERS</title> 560 <para> 561 When Unix Extensions are enabled, we use the actual inode 562 number provided by the server in response to the POSIX calls as an 563 inode number. 564 </para> 565 <para> 566 When Unix Extensions are disabled and "serverino" mount option 567 is enabled there is no way to get the server inode number. The 568 client typically maps the server-assigned "UniqueID" onto an inode 569 number. 570 </para> 571 <para> 572 Note that the UniqueID is a different value from the server 573 inode number. The UniqueID value is unique over the scope of the entire 574 server and is often greater than 2 power 32. This value often makes 575 programs that are not compiled with LFS (Large File Support), to 576 trigger a glibc EOVERFLOW error as this won't fit in the target 577 structure field. It is strongly recommended to compile your programs 578 with LFS support (i.e. with -D_FILE_OFFSET_BITS=64) to prevent this 579 problem. You can also use "noserverino" mount option to generate inode 580 numbers smaller than 2 power 32 on the client. But you may not be able 581 to detect hardlinks properly. 582 </para> 583</refsect1> 584 585<refsect1> 586 <title>FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS</title> 587 588 <para> The core CIFS protocol does not provide unix ownership 589information or mode for files and directories. Because of this, files 590and directories will generally appear to be owned by whatever values the 591uid= or gid= options are set, and will have permissions set to the 592default file_mode and dir_mode for the mount. Attempting to change these 593values via chmod/chown will return success but have no effect.</para> 594 595 <para>When the client and server negotiate unix extensions, 596files and directories will be assigned the uid, gid, and mode provided 597by the server. Because CIFS mounts are generally single-user, and the 598same credentials are used no matter what user accesses the mount, newly 599created files and directories will generally be given ownership 600corresponding to whatever credentials were used to mount the 601share.</para> 602 603 <para>If the uid's and gid's being used do not match on the 604client and server, the forceuid and forcegid options may be helpful. 605Note however, that there is no corresponding option to override the 606mode. Permissions assigned to a file when forceuid or forcegid are in 607effect may not reflect the the real permissions.</para> 608 609 <para>When unix extensions are not negotiated, it's also 610possible to emulate them locally on the server using the "dynperm" mount 611option. When this mount option is in effect, newly created files and 612directories will receive what appear to be proper permissions. These 613permissions are not stored on the server however and can disappear at 614any time in the future (subject to the whims of the kernel flushing out 615the inode cache). In general, this mount option is discouraged. 616 </para> 617 618 <para>It's also possible to override permission checking on the client 619altogether via the noperm option. Server-side permission checks cannot be 620overriden. The permission checks done by the server will always correspond to 621the credentials used to mount the share, and not necessarily to the user who is accessing the share.</para> 622 623</refsect1> 624 625<refsect1> 626 <title>ENVIRONMENT VARIABLES</title> 627 628 <para> 629 The variable <emphasis>USER</emphasis> may contain the username of the 630person to be used to authenticate to the server. 631The variable can be used to set both username and 632password by using the format username%password. 633 </para> 634 635 <para> 636 The variable <emphasis>PASSWD</emphasis> may contain the password of the 637person using the client. 638 </para> 639 640 <para> 641 The variable <emphasis>PASSWD_FILE</emphasis> may contain the pathname 642of a file to read the password from. A single line of input is 643read and used as the password. 644 </para> 645 646</refsect1> 647 648<refsect1> 649 <title>NOTES</title> 650 651 <para>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.</para> 652 653 <para> 654 Some samba client tools like smbclient(8) honour client-side 655 configuration parameters present in smb.conf. Unlike those 656 client tools, <emphasis>mount.cifs</emphasis> ignores smb.conf 657 completely. 658 </para> 659 660</refsect1> 661 662<refsect1> 663 <title>CONFIGURATION</title> 664 <para> 665The primary mechanism for making configuration changes and for reading 666debug information for the cifs vfs is via the Linux /proc filesystem. 667In the directory <filename>/proc/fs/cifs</filename> are various 668configuration files and pseudo files which can display debug information. 669There are additional startup options such as maximum buffer size and number 670of buffers which only may be set when the kernel cifs vfs (cifs.ko module) is 671loaded. These can be seen by running the modinfo utility against the file 672cifs.ko which will list the options that may be passed to cifs during module 673installation (device driver load). 674For more information see the kernel file <filename>fs/cifs/README</filename>. 675</para> 676</refsect1> 677 678<refsect1> 679 <title>BUGS</title> 680 681 <para>Mounting using the CIFS URL specification is currently not supported. 682 </para> 683 684 <para>The credentials file does not handle usernames or passwords with 685 leading space.</para> 686 687 <para> 688Note that the typical response to a bug report is a suggestion 689to try the latest version first. So please try doing that first, 690and always include which versions you use of relevant software 691when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and 692server type you are trying to contact. 693</para> 694</refsect1> 695 696 697 698<refsect1> 699 <title>VERSION</title> 700 701 <para>This man page is correct for version 1.52 of 702 the cifs vfs filesystem (roughly Linux kernel 2.6.24).</para> 703</refsect1> 704 705<refsect1> 706 <title>SEE ALSO</title> 707 <para> 708 Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel 709 source tree may contain additional options and information. 710</para> 711 <para><citerefentry><refentrytitle>umount.cifs</refentrytitle> 712 <manvolnum>8</manvolnum></citerefentry></para> 713 714</refsect1> 715 716<refsect1> 717 <title>AUTHOR</title> 718 719 <para>Steve French</para> 720 721 <para>The syntax and manpage were loosely based on that of smbmount. It 722 was converted to Docbook/XML by Jelmer Vernooij.</para> 723 724 <para>The maintainer of the Linux cifs vfs and the userspace 725 tool <emphasis>mount.cifs</emphasis> is <ulink url="mailto:sfrench@samba.org">Steve French</ulink>. 726 The <ulink url="mailto:linux-cifs-client@lists.samba.org">Linux CIFS Mailing list</ulink> 727 is the preferred place to ask questions regarding these programs. 728 </para> 729 730</refsect1> 731 732</refentry> 733