Ignore:
Timestamp:
May 27, 2007, 12:26:26 AM (18 years ago)
Author:
Paul Smedley
Message:

Upgrade source to 3.0.25a

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/samba/docs/manpages/mount.cifs.8

    r1 r39  
    1919..
    2020.TH "MOUNT.CIFS" 8 "" "" ""
    21 .SH NAME
    22 mount.cifs \- mount using the Common Internet File System (CIFS)
     21.SH "NAME"
     22mount.cifs - mount using the Common Internet File System (CIFS)
    2323.SH "SYNOPSIS"
    24 .ad l
    25 .hy 0
    2624.HP 11
    27 \fBmount\&.cifs\fR {service} {mount\-point} [\-o\ options]
    28 .ad
    29 .hy
    30 
     25\fBmount.cifs\fR {service} {mount-point} [-o options]
    3126.SH "DESCRIPTION"
    32 
    33 .PP
    34 This tool is part of the \fBsamba\fR(7) suite\&.
    35 
    36 .PP
    37 mount\&.cifs mounts a Linux CIFS filesystem\&. It is usually invoked indirectly by the \fBmount\fR(8) command when using the "\-t cifs" option\&. This command only works in Linux, and the kernel must support the cifs filesystem\&. The CIFS protocol is the successor to the SMB protocol and is supported by most Windows servers and many other commercial servers and Network Attached Storage appliances as well as by the popular Open Source server Samba\&.
    38 
    39 .PP
    40 The mount\&.cifs utility attaches the UNC name (exported network resource) to the local directory \fBmount\-point\fR\&. It is possible to set the mode for mount\&.cifs to setuid root to allow non\-root users to mount shares to directories for which they have write permission\&.
    41 
    42 .PP
    43 Options to \fBmount\&.cifs\fR are specified as a comma\-separated list of key=value pairs\&. It is possible to send options other than those listed here, assuming that the cifs filesystem kernel module (cifs\&.ko) supports them\&. Unrecognized cifs mount options passed to the cifs vfs kernel code will be logged to the kernel log\&.
    44 
    45 .PP
    46 \fBmount\&.cifs\fR causes the cifs vfs to launch a thread named cifsd\&. After mounting it keeps running until the mounted resource is unmounted (usually via the umount utility)\&.
    47 
     27.PP
     28This tool is part of the
     29\fBsamba\fR(7)
     30suite.
     31.PP
     32mount.cifs mounts a Linux CIFS filesystem. It is usually invoked indirectly by the
     33\fBmount\fR(8)
     34command when using the "-t cifs" option. This command only works in Linux, and the kernel must support the cifs filesystem. The CIFS protocol is the successor to the SMB protocol and is supported by most Windows servers and many other commercial servers and Network Attached Storage appliances as well as by the popular Open Source server Samba.
     35.PP
     36The mount.cifs utility attaches the UNC name (exported network resource) to the local directory
     37\fBmount-point\fR. It is possible to set the mode for mount.cifs to setuid root to allow non-root users to mount shares to directories for which they have write permission.
     38.PP
     39Options to
     40\fBmount.cifs\fR
     41are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that the cifs filesystem kernel module (cifs.ko) supports them. Unrecognized cifs mount options passed to the cifs vfs kernel code will be logged to the kernel log.
     42.PP
     43\fBmount.cifs\fR
     44causes the cifs vfs to launch a thread named cifsd. After mounting it keeps running until the mounted resource is unmounted (usually via the umount utility).
    4845.SH "OPTIONS"
    49 
    50 .TP
     46.PP
    5147user=\fIarg\fR
    52 specifies the username to connect as\&. If this is not given, then the environment variable \fBUSER\fR is used\&. This option can also take the form "user%password" or "workgroup/user" or "workgroup/user%password" to allow the password and workgroup to be specified as part of the username\&.
    53 
    54 .RS
    55 .Sh "Note"
    56 The cifs vfs accepts the parameter \fIuser=\fR, or for users familiar with smbfs it accepts the longer form of the parameter \fIusername=\fR\&. Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters \fIpass=\fR,\fIdom=\fR and \fIcred=\fR\&.
    57 
    58 .RE
    59 
    60 .TP
     48.RS 3n
     49specifies the username to connect as. If this is not given, then the environment variable
     50\fBUSER\fR
     51is used. This option can also take the form "user%password" or "workgroup/user" or "workgroup/user%password" to allow the password and workgroup to be specified as part of the username.
     52.sp
     53.it 1 an-trap
     54.nr an-no-space-flag 1
     55.nr an-break-flag 1
     56.br
     57\fBNote\fR
     58The cifs vfs accepts the parameter
     59\fIuser=\fR, or for users familiar with smbfs it accepts the longer form of the parameter
     60\fIusername=\fR. Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters
     61\fIpass=\fR,\fIdom=\fR
     62and
     63\fIcred=\fR.
     64.RE
     65.PP
    6166password=\fIarg\fR
    62 specifies the CIFS password\&. If this option is not given then the environment variable \fBPASSWD\fR is used\&. If the password is not specified directly or indirectly via an argument to mount \fBmount\&.cifs\fR will prompt for a password, unless the guest option is specified\&.
    63 
    64 Note that a password which contains the delimiter character (i\&.e\&. a comma ',') will fail to be parsed correctly on the command line\&. However, the same password defined in the PASSWD environment variable or via a credentials file (see below) or entered at the password prompt will be read correctly\&.
    65 
    66 .TP
     67.RS 3n
     68specifies the CIFS password. If this option is not given then the environment variable
     69\fBPASSWD\fR
     70is used. If the password is not specified directly or indirectly via an argument to mount
     71\fBmount.cifs\fR
     72will prompt for a password, unless the guest option is specified.
     73.sp
     74Note that a password which contains the delimiter character (i.e. a comma ',') will fail to be parsed correctly on the command line. However, the same password defined in the PASSWD environment variable or via a credentials file (see below) or entered at the password prompt will be read correctly.
     75.RE
     76.PP
    6777credentials=\fIfilename\fR
    68 specifies a file that contains a username and/or password\&. The format of the file is:
    69 
     78.RS 3n
     79specifies a file that contains a username and/or password. The format of the file is:
    7080
    7181.nf
    … …  
    7585
    7686.fi
    77 This is preferred over having passwords in plaintext in a shared file, such as \fI/etc/fstab\fR\&. Be sure to protect any credentials file properly\&.
     87This is preferred over having passwords in plaintext in a shared file, such as
     88\fI/etc/fstab\fR. Be sure to protect any credentials file properly.
     89.RE
     90.PP
     91uid=\fIarg\fR
     92.RS 3n
     93sets the uid that will own all files on the mounted filesystem. It may be specified as either a username or a numeric uid. This parameter is ignored when the target server supports the CIFS Unix extensions.
     94.RE
     95.PP
     96gid=\fIarg\fR
     97.RS 3n
     98sets the gid that will own all files on the mounted filesystem. It may be specified as either a groupname or a numeric gid. This parameter is ignored when the target server supports the CIFS Unix extensions.
     99.RE
     100.PP
     101port=\fIarg\fR
     102.RS 3n
     103sets the port number on the server to attempt to contact to negotiate CIFS support. If the CIFS server is not listening on this port or if it is not specified, the default ports will be tried i.e. port 445 is tried and if no response then port 139 is tried.
     104.RE
     105.PP
     106netbiosname=\fIarg\fR
     107.RS 3n
     108When mounting to servers via port 139, specifies the RFC1001 source name to use to represent the client netbios machine name when doing the RFC1001 netbios session initialize.
     109.RE
     110.PP
     111file_mode=\fIarg\fR
     112.RS 3n
     113If the server does not support the CIFS Unix extensions this overrides the default file mode.
     114.RE
     115.PP
     116dir_mode=\fIarg\fR
     117.RS 3n
     118If the server does not support the CIFS Unix extensions this overrides the default mode for directories.
     119.RE
     120.PP
     121ip=\fIarg\fR
     122.RS 3n
     123sets the destination host or IP address.
     124.RE
     125.PP
     126domain=\fIarg\fR
     127.RS 3n
     128sets the domain (workgroup) of the user
     129.RE
     130.PP
     131guest
     132.RS 3n
     133don't prompt for a password
     134.RE
     135.PP
     136iocharset
     137.RS 3n
     138Charset used to convert local path names to and from Unicode. Unicode is used by default for network path names if the server supports it. If iocharset is not specified then the nls_default specified during the local client kernel build will be used. If server does not support Unicode, this parameter is unused.
     139.RE
     140.PP
     141ro
     142.RS 3n
     143mount read-only
     144.RE
     145.PP
     146rw
     147.RS 3n
     148mount read-write
     149.RE
     150.PP
     151setuids
     152.RS 3n
     153If the CIFS Unix extensions are negotiated with the server the client will attempt to set the effective uid and gid of the local process on newly created files, directories, and devices (create, mkdir, mknod). If the CIFS Unix Extensions are not negotiated, for newly created files and directories instead of using the default uid and gid specified on the the mount, cache the new file's uid and gid locally which means that the uid for the file can change when the inode is reloaded (or the user remounts the share).
     154.RE
     155.PP
     156nosetuids
     157.RS 3n
     158The client will not attempt to set the uid and gid on on newly created files, directories, and devices (create, mkdir, mknod) which will result in the server setting the uid and gid to the default (usually the server uid of the user who mounted the share). Letting the server (rather than the client) set the uid and gid is the default.If the CIFS Unix Extensions are not negotiated then the uid and gid for new files will appear to be the uid (gid) of the mounter or the uid (gid) parameter specified on the mount.
     159.RE
     160.PP
     161perm
     162.RS 3n
     163Client does permission checks (vfs_permission check of uid and gid of the file against the mode and desired operation), Note that this is in addition to the normal ACL check on the target machine done by the server software. Client permission checking is enabled by default.
     164.RE
     165.PP
     166noperm
     167.RS 3n
     168Client does not do permission checks. This can expose files on this mount to access by other users on the local client system. It is typically only needed when the server supports the CIFS Unix Extensions but the UIDs/GIDs on the client and server system do not match closely enough to allow access by the user doing the mount. Note that this does not affect the normal ACL check on the target machine done by the server software (of the server ACL against the user name provided at mount time).
     169.RE
     170.PP
     171directio
     172.RS 3n
     173Do not do inode data caching on files opened on this mount. This precludes mmaping files on this mount. In some cases with fast networks and little or no caching benefits on the client (e.g. when the application is doing large sequential reads bigger than page size without rereading the same data) this can provide better performance than the default behavior which caches reads (readahead) and writes (writebehind) through the local Linux client pagecache if oplock (caching token) is granted and held. Note that direct allows write operations larger than page size to be sent to the server. On some kernels this requires the cifs.ko module to be built with the CIFS_EXPERIMENTAL configure option.
     174.RE
     175.PP
     176mapchars
     177.RS 3n
     178Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters) to the remap range (above 0xF000), which also allows the CIFS client to recognize files created with such characters by Windows's POSIX emulation. This can also be useful when mounting to most versions of Samba (which also forbids creating and opening files whose names contain any of these seven characters). This has no effect if the server does not support Unicode on the wire.
     179.RE
     180.PP
     181nomapchars
     182.RS 3n
     183Do not translate any of these seven characters (default)
     184.RE
     185.PP
     186intr
     187.RS 3n
     188currently unimplemented
     189.RE
     190.PP
     191nointr
     192.RS 3n
     193(default) currently unimplemented
     194.RE
     195.PP
     196hard
     197.RS 3n
     198The program accessing a file on the cifs mounted file system will hang when the server crashes.
     199.RE
     200.PP
     201soft
     202.RS 3n
     203(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.
     204.RE
     205.PP
     206noacl
     207.RS 3n
     208Do not allow POSIX ACL operations even if server would support them.
     209.sp
     210The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers version 3.10 and later. Setting POSIX ACLs requires enabling both XATTR and then POSIX support in the CIFS configuration options when building the cifs module. POSIX ACL support can be disabled on a per mount basic by specifying "noacl" on mount.
     211.RE
     212.PP
     213nocase
     214.RS 3n
     215Request case insensitive path name matching (case sensitive is the default if the server suports it).
     216.RE
     217.PP
     218sec=
     219.RS 3n
     220Security mode. Allowed values are:
     221.RS 3n
     222.TP 3n
     223•
     224none attempt to connection as a null user (no name)
     225.TP 3n
     226•
     227krb5 Use Kerberos version 5 authentication
     228.TP 3n
     229•
     230krb5i Use Kerberos authentication and packet signing
     231.TP 3n
     232•
     233ntlm Use NTLM password hashing (default)
     234.TP 3n
     235•
     236ntlmi Use NTLM password hashing with signing (if /proc/fs/cifs/PacketSigningEnabled on or if server requires signing also can be the default)
     237.TP 3n
     238•
     239ntlmv2 Use NTLMv2 password hashing
     240.TP 3n
     241•
     242ntlmv2i Use NTLMv2 password hashing with packet signing
     243.RE
     244.IP "" 3n
     245[NB This [sec parameter] is under development and expected to be available in cifs kernel module 1.40 and later]
     246.RE
     247.PP
     248nobrl
     249.RS 3n
     250Do not send byte range lock requests to the server. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most cifs servers do not yet support requesting advisory byte range locks).
     251.RE
     252.PP
     253sfu
     254.RS 3n
     255When the CIFS Unix Extensions are not negotiated, attempt to create device files and fifos in a format compatible with Services for Unix (SFU). In addition retrieve bits 10-12 of the mode via the SETFILEBITS extended attribute (as SFU does). In the future the bottom 9 bits of the mode mode also will be emulated using queries of the security descriptor (ACL). [NB: requires version 1.39 or later of the CIFS VFS. To recognize symlinks and be able to create symlinks in an SFU interoperable form requires version 1.40 or later of the CIFS VFS kernel module.
     256.RE
     257.PP
     258serverino
     259.RS 3n
     260Use inode numbers (unique persistent file identifiers) returned by the server instead of automatically generating temporary inode numbers on the client. Although server inode numbers make it easier to spot hardlinked files (as they will have the same inode numbers) and inode numbers may be persistent (which is userful for some sofware), the server does not guarantee that the inode numbers are unique if multiple server side mounts are exported under a single share (since inode numbers on the servers might not be unique if multiple filesystems are mounted under the same shared higher level directory). Note that not all servers support returning server inode numbers, although those that support the CIFS Unix Extensions, and Windows 2000 and later servers typically do support this (although not necessarily on every local server filesystem). Parameter has no effect if the server lacks support for returning inode numbers or equivalent.
     261.RE
     262.PP
     263noserverino
     264.RS 3n
     265client generates inode numbers (rather than using the actual one from the server) by default.
     266.RE
     267.PP
     268nouser_xattr
     269.RS 3n
     270(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise.
     271.RE
     272.PP
     273rsize=\fIarg\fR
     274.RS 3n
     275default network read size
     276.RE
     277.PP
     278wsize=\fIarg\fR
     279.RS 3n
     280default network write size
     281.RE
     282.PP
     283--verbose
     284.RS 3n
     285Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:
     286.sp
     287mount -t cifs //server/share /mnt --verbose -o user=username
     288.RE
     289.SH "ENVIRONMENT VARIABLES"
     290.PP
     291The variable
     292\fBUSER\fR
     293may contain the username of the person to be used to authenticate to the server. The variable can be used to set both username and password by using the format username%password.
     294.PP
     295The variable
     296\fBPASSWD\fR
     297may contain the password of the person using the client.
     298.PP
     299The variable
     300\fBPASSWD_FILE\fR
     301may contain the pathname of a file to read the password from. A single line of input is read and used as the password.
     302.SH "NOTES"
     303.PP
     304This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.
     305.SH "CONFIGURATION"
     306.PP
     307The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem. In the directory
     308\fI/proc/fs/cifs\fR
     309are various configuration files and pseudo files which can display debug information. There are additional startup options such as maximum buffer size and number of buffers which only may be set when the kernel cifs vfs (cifs.ko module) is loaded. These can be seen by running the modinfo utility against the file cifs.ko which will list the options that may be passed to cifs during module installation (device driver load). For more information see the kernel file
     310\fIfs/cifs/README\fR.
     311.SH "BUGS"
     312.PP
     313Mounting using the CIFS URL specification is currently not supported.
     314.PP
     315The credentials file does not handle usernames or passwords with leading space.
     316.PP
     317Note that the typical response to a bug report is a suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and server type you are trying to contact.
     318.SH "VERSION"
     319.PP
     320This man page is correct for version 1.39 of the cifs vfs filesystem (roughly Linux kernel 2.6.15).
     321.SH "SEE ALSO"
     322.PP
     323Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information.
     324.PP
     325\fBumount.cifs\fR(8)
     326.SH "AUTHOR"
     327.PP
     328Steve French
     329.PP
     330The syntax and manpage were loosely based on that of smbmount. It was converted to Docbook/XML by Jelmer Vernooij.
     331.PP
     332The maintainer of the Linux cifs vfs and the userspace tool
     333\fBmount.cifs\fR
     334is
     335Steve French. The
     336Linux CIFS Mailing list
     337is the preferred place to ask questions regarding these programs.
    78338
    79 .TP
    80 uid=\fIarg\fR
    81 sets the uid that will own all files on the mounted filesystem\&. It may be specified as either a username or a numeric uid\&. This parameter is ignored when the target server supports the CIFS Unix extensions\&.
    82 
    83 .TP
    84 gid=\fIarg\fR
    85 sets the gid that will own all files on the mounted filesystem\&. It may be specified as either a groupname or a numeric gid\&. This parameter is ignored when the target server supports the CIFS Unix extensions\&.
    86 
    87 .TP
    88 port=\fIarg\fR
    89 sets the port number on the server to attempt to contact to negotiate CIFS support\&. If the CIFS server is not listening on this port or if it is not specified, the default ports will be tried i\&.e\&. port 445 is tried and if no response then port 139 is tried\&.
    90 
    91 .TP
    92 netbiosname=\fIarg\fR
    93 When mounting to servers via port 139, specifies the RFC1001 source name to use to represent the client netbios machine name when doing the RFC1001 netbios session initialize\&.
    94 
    95 .TP
    96 file_mode=\fIarg\fR
    97 If the server does not support the CIFS Unix extensions this overrides the default file mode\&.
    98 
    99 .TP
    100 dir_mode=\fIarg\fR
    101 If the server does not support the CIFS Unix extensions this overrides the default mode for directories\&.
    102 
    103 .TP
    104 ip=\fIarg\fR
    105 sets the destination host or IP address\&.
    106 
    107 .TP
    108 domain=\fIarg\fR
    109 sets the domain (workgroup) of the user
    110 
    111 .TP
    112 guest
    113 don't prompt for a password
    114 
    115 .TP
    116 iocharset
    117 Charset used to convert local path names to and from Unicode\&. Unicode is used by default for network path names if the server supports it\&. If iocharset is not specified then the nls_default specified during the local client kernel build will be used\&. If server does not support Unicode, this parameter is unused\&.
    118 
    119 .TP
    120 ro
    121 mount read\-only
    122 
    123 .TP
    124 rw
    125 mount read\-write
    126 
    127 .TP
    128 setuids
    129 If the CIFS Unix extensions are negotiated with the server the client will attempt to set the effective uid and gid of the local process on newly created files, directories, and devices (create, mkdir, mknod)\&. If the CIFS Unix Extensions are not negotiated, for newly created files and directories instead of using the default uid and gid specified on the the mount, cache the new file's uid and gid locally which means that the uid for the file can change when the inode is reloaded (or the user remounts the share)\&.
    130 
    131 .TP
    132 nosetuids
    133 The client will not attempt to set the uid and gid on on newly created files, directories, and devices (create, mkdir, mknod) which will result in the server setting the uid and gid to the default (usually the server uid of the user who mounted the share)\&. Letting the server (rather than the client) set the uid and gid is the default\&.If the CIFS Unix Extensions are not negotiated then the uid and gid for new files will appear to be the uid (gid) of the mounter or the uid (gid) parameter specified on the mount\&.
    134 
    135 .TP
    136 perm
    137 Client does permission checks (vfs_permission check of uid and gid of the file against the mode and desired operation), Note that this is in addition to the normal ACL check on the target machine done by the server software\&. Client permission checking is enabled by default\&.
    138 
    139 .TP
    140 noperm
    141 Client does not do permission checks\&. This can expose files on this mount to access by other users on the local client system\&. It is typically only needed when the server supports the CIFS Unix Extensions but the UIDs/GIDs on the client and server system do not match closely enough to allow access by the user doing the mount\&. Note that this does not affect the normal ACL check on the target machine done by the server software (of the server ACL against the user name provided at mount time)\&.
    142 
    143 .TP
    144 directio
    145 Do not do inode data caching on files opened on this mount\&. This precludes mmaping files on this mount\&. In some cases with fast networks and little or no caching benefits on the client (e\&.g\&. when the application is doing large sequential reads bigger than page size without rereading the same data) this can provide better performance than the default behavior which caches reads (readahead) and writes (writebehind) through the local Linux client pagecache if oplock (caching token) is granted and held\&. Note that direct allows write operations larger than page size to be sent to the server\&. On some kernels this requires the cifs\&.ko module to be built with the CIFS_EXPERIMENTAL configure option\&.
    146 
    147 .TP
    148 mapchars
    149 Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters) to the remap range (above 0xF000), which also allows the CIFS client to recognize files created with such characters by Windows's POSIX emulation\&. This can also be useful when mounting to most versions of Samba (which also forbids creating and opening files whose names contain any of these seven characters)\&. This has no effect if the server does not support Unicode on the wire\&.
    150 
    151 .TP
    152 nomapchars
    153 Do not translate any of these seven characters (default)
    154 
    155 .TP
    156 intr
    157 currently unimplemented
    158 
    159 .TP
    160 nointr
    161 (default) currently unimplemented
    162 
    163 .TP
    164 hard
    165 The program accessing a file on the cifs mounted file system will hang when the server crashes\&.
    166 
    167 .TP
    168 soft
    169 (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\&.
    170 
    171 .TP
    172 noacl
    173 Do not allow POSIX ACL operations even if server would support them\&.
    174 
    175 The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers version 3\&.10 and later\&. Setting POSIX ACLs requires enabling both XATTR and then POSIX support in the CIFS configuration options when building the cifs module\&. POSIX ACL support can be disabled on a per mount basic by specifying "noacl" on mount\&.
    176 
    177 .TP
    178 nocase
    179 Request case insensitive path name matching (case sensitive is the default if the server suports it)\&.
    180 
    181 .TP
    182 sec=
    183 Security mode\&. Allowed values are:
    184 
    185 
    186 .RS
    187 .TP 3
    188 \(bu
    189 none attempt to connection as a null user (no name)
    190 .TP
    191 \(bu
    192 krb5 Use Kerberos version 5 authentication
    193 .TP
    194 \(bu
    195 krb5i Use Kerberos authentication and packet signing
    196 .TP
    197 \(bu
    198 ntlm Use NTLM password hashing (default)
    199 .TP
    200 \(bu
    201 ntlmi Use NTLM password hashing with signing (if /proc/fs/cifs/PacketSigningEnabled on or if server requires signing also can be the default)
    202 .TP
    203 \(bu
    204 ntlmv2 Use NTLMv2 password hashing
    205 .TP
    206 \(bu
    207 ntlmv2i Use NTLMv2 password hashing with packet signing
    208 .LP
    209 .RE
    210 .IP
    211 [NB This [sec parameter] is under development and expected to be available in cifs kernel module 1\&.40 and later]
    212 
    213 .TP
    214 nobrl
    215 Do not send byte range lock requests to the server\&. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most cifs servers do not yet support requesting advisory byte range locks)\&.
    216 
    217 .TP
    218 sfu
    219 When the CIFS Unix Extensions are not negotiated, attempt to create device files and fifos in a format compatible with Services for Unix (SFU)\&. In addition retrieve bits 10\-12 of the mode via the SETFILEBITS extended attribute (as SFU does)\&. In the future the bottom 9 bits of the mode mode also will be emulated using queries of the security descriptor (ACL)\&. [NB: requires version 1\&.39 or later of the CIFS VFS\&. To recognize symlinks and be able to create symlinks in an SFU interoperable form requires version 1\&.40 or later of the CIFS VFS kernel module\&.
    220 
    221 .TP
    222 serverino
    223 Use inode numbers (unique persistent file identifiers) returned by the server instead of automatically generating temporary inode numbers on the client\&. Although server inode numbers make it easier to spot hardlinked files (as they will have the same inode numbers) and inode numbers may be persistent (which is userful for some sofware), the server does not guarantee that the inode numbers are unique if multiple server side mounts are exported under a single share (since inode numbers on the servers might not be unique if multiple filesystems are mounted under the same shared higher level directory)\&. Note that not all servers support returning server inode numbers, although those that support the CIFS Unix Extensions, and Windows 2000 and later servers typically do support this (although not necessarily on every local server filesystem)\&. Parameter has no effect if the server lacks support for returning inode numbers or equivalent\&.
    224 
    225 .TP
    226 noserverino
    227 client generates inode numbers (rather than using the actual one from the server) by default\&.
    228 
    229 .TP
    230 nouser_xattr
    231 (default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise\&.
    232 
    233 .TP
    234 rsize=\fIarg\fR
    235 default network read size
    236 
    237 .TP
    238 wsize=\fIarg\fR
    239 default network write size
    240 
    241 .TP
    242 \-\-verbose
    243 Print additional debugging information for the mount\&. Note that this parameter must be specified before the \-o\&. For example:
    244 
    245 mount \-t cifs //server/share /mnt \-\-verbose \-o user=username
    246 
    247 .SH "ENVIRONMENT VARIABLES"
    248 
    249 .PP
    250 The variable \fBUSER\fR may contain the username of the person to be used to authenticate to the server\&. The variable can be used to set both username and password by using the format username%password\&.
    251 
    252 .PP
    253 The variable \fBPASSWD\fR may contain the password of the person using the client\&.
    254 
    255 .PP
    256 The variable \fBPASSWD_FILE\fR may contain the pathname of a file to read the password from\&. A single line of input is read and used as the password\&.
    257 
    258 .SH "NOTES"
    259 
    260 .PP
    261 This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled\&.
    262 
    263 .SH "CONFIGURATION"
    264 
    265 .PP
    266 The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem\&. In the directory \fI/proc/fs/cifs\fR are various configuration files and pseudo files which can display debug information\&. There are additional startup options such as maximum buffer size and number of buffers which only may be set when the kernel cifs vfs (cifs\&.ko module) is loaded\&. These can be seen by running the modinfo utility against the file cifs\&.ko which will list the options that may be passed to cifs during module installation (device driver load)\&. For more information see the kernel file \fIfs/cifs/README\fR\&.
    267 
    268 .SH "BUGS"
    269 
    270 .PP
    271 Mounting using the CIFS URL specification is currently not supported\&.
    272 
    273 .PP
    274 The credentials file does not handle usernames or passwords with leading space\&.
    275 
    276 .PP
    277 Note that the typical response to a bug report is a suggestion to try the latest version first\&. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: mount\&.cifs (try mount\&.cifs \-V), kernel (see /proc/version) and server type you are trying to contact\&.
    278 
    279 .SH "VERSION"
    280 
    281 .PP
    282 This man page is correct for version 1\&.39 of the cifs vfs filesystem (roughly Linux kernel 2\&.6\&.15)\&.
    283 
    284 .SH "SEE ALSO"
    285 
    286 .PP
    287 Documentation/filesystems/cifs\&.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information\&.
    288 
    289 .PP
    290 \fBumount\&.cifs\fR(8)
    291 
    292 .SH "AUTHOR"
    293 
    294 .PP
    295 Steve French
    296 
    297 .PP
    298 The syntax and manpage were loosely based on that of smbmount\&. It was converted to Docbook/XML by Jelmer Vernooij\&.
    299 
    300 .PP
    301 The maintainer of the Linux cifs vfs and the userspace tool \fBmount\&.cifs\fR is Steve French\&. The Linux CIFS Mailing list is the preferred place to ask questions regarding these programs\&.
    302 
Note: See TracChangeset for help on using the changeset viewer.