Changeset 134 for branches/samba-3.0/docs/manpages/mount.cifs.8
- Timestamp:
- May 23, 2008, 6:56:41 AM (17 years ago)
- File:
-
- 1 edited
-
branches/samba-3.0/docs/manpages/mount.cifs.8 (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/manpages/mount.cifs.8
r44 r134 1 .\"Generated by db2man.xsl. Don't modify this, modify the source. 2 .de Sh \" Subsection 3 .br 4 .if t .Sp 5 .ne 5 6 .PP 7 \fB\\$1\fR 8 .PP 9 .. 10 .de Sp \" Vertical space (when we can't use .PP) 11 .if t .sp .5v 12 .if n .sp 13 .. 14 .de Ip \" List item 15 .br 16 .ie \\n(.$>=3 .ne \\$3 17 .el .ne 3 18 .IP "\\$1" \\$2 19 .. 20 .TH "MOUNT.CIFS" 8 "" "" "" 1 .\" Title: mount.cifs 2 .\" Author: 3 .\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/> 4 .\" Date: 05/21/2008 5 .\" Manual: System Administration tools 6 .\" Source: Samba 3.0 7 .\" 8 .TH "MOUNT\.CIFS" "8" "05/21/2008" "Samba 3\.0" "System Administration tools" 9 .\" disable hyphenation 10 .nh 11 .\" disable justification (adjust text to left margin only) 12 .ad l 21 13 .SH "NAME" 22 14 mount.cifs - mount using the Common Internet File System (CIFS) 23 15 .SH "SYNOPSIS" 24 16 .HP 1 25 mount .cifs {service} {mount-point} [-ooptions]17 mount\.cifs {service} {mount\-point} [\-o\ options] 26 18 .SH "DESCRIPTION" 27 19 .PP 28 20 This tool is part of the 29 21 \fBsamba\fR(7) 30 suite .31 .PP 32 mount .cifs mounts a Linux CIFS filesystem. It is usually invoked indirectly by the22 suite\. 23 .PP 24 mount\.cifs mounts a Linux CIFS filesystem\. It is usually invoked indirectly by the 33 25 \fBmount\fR(8) 34 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.35 .PP 36 The mount .cifs utility attaches the UNC name (exported network resource) to the local directory37 \f Bmount-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.26 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\. 27 .PP 28 The mount\.cifs utility attaches the UNC name (exported network resource) to the local directory 29 \fImount\-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 30 .PP 39 31 Options to 40 \f Bmount.cifs\fR41 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.42 .PP 43 \f Bmount.cifs\fR44 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).32 \fImount\.cifs\fR 33 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\. 34 .PP 35 \fImount\.cifs\fR 36 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)\. 45 37 .SH "OPTIONS" 46 38 .PP 47 39 user=\fIarg\fR 48 .RS 3n49 specifies the username to connect as . If this is not given, then the environment variable50 \f BUSER\fR51 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.40 .RS 4 41 specifies the username to connect as\. If this is not given, then the environment variable 42 \fIUSER\fR 43 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\. 52 44 .sp 53 45 .it 1 an-trap … … 55 47 .nr an-break-flag 1 56 48 .br 57 \fBNote\fR 49 Note 58 50 The cifs vfs accepts the parameter 59 51 \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 parameters52 \fIusername=\fR\. Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters 61 53 \fIpass=\fR,\fIdom=\fR 62 54 and 63 \fIcred=\fR .55 \fIcred=\fR\. 64 56 .RE 65 57 .PP 66 58 password=\fIarg\fR 67 .RS 3n68 specifies the CIFS password . If this option is not given then the environment variable69 \f BPASSWD\fR70 is used . If the password is not specified directly or indirectly via an argument to mount71 \f Bmount.cifs\fR72 will prompt for a password, unless the guest option is specified .73 .sp 74 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.59 .RS 4 60 specifies the CIFS password\. If this option is not given then the environment variable 61 \fIPASSWD\fR 62 is used\. If the password is not specified directly or indirectly via an argument to mount, 63 \fImount\.cifs\fR 64 will prompt for a password, unless the guest option is specified\. 65 .sp 66 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\. 75 67 .RE 76 68 .PP 77 69 credentials=\fIfilename\fR 78 .RS 3n 79 specifies a file that contains a username and/or password. The format of the file is: 80 70 .RS 4 71 specifies a file that contains a username and/or password\. The format of the file is: 72 .sp 73 .RS 4 81 74 .nf 82 83 75 username=\fIvalue\fR 84 76 password=\fIvalue\fR 85 86 77 .fi 78 .RE 87 79 This 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.80 \fI/etc/fstab\fR\. Be sure to protect any credentials file properly\. 89 81 .RE 90 82 .PP 91 83 uid=\fIarg\fR 92 .RS 3n93 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.84 .RS 4 85 sets the uid that will own all files on the mounted filesystem\. It may be specified as either a username or a numeric uid\. For mounts to servers which do support the CIFS Unix extensions, such as a properly configured Samba server, the server provides the uid, gid and mode so this parameter should not be specified unless the server and client uid and gid numbering differ\. If the server and client are in the same domain (e\.g\. running winbind or nss_ldap) and the server supports the Unix Extensions then the uid and gid can be retrieved from the server (and uid and gid would not have to be specifed on the mount\. For servers which do not support the CIFS Unix extensions, the default uid (and gid) returned on lookup of existing files will be the uid (gid) of the person who executed the mount (root, except when mount\.cifs is configured setuid for user mounts) unless the "uid=" (gid) mount option is specified\. For the uid (gid) of newly created files and directories, ie files created since the last mount of the server share, the expected uid (gid) is cached as long as the inode remains in memory on the client\. Also note that permission checks (authorization checks) on accesses to a file occur at the server, but there are cases in which an administrator may want to restrict at the client as well\. For those servers which do not report a uid/gid owner (such as Windows), permissions can also be checked at the client, and a crude form of client side permission checking can be enabled by specifying file_mode and dir_mode on the client\. Note that the mount\.cifs helper must be at version 1\.10 or higher to support specifying the uid (or gid) in non\-numeric form\. 94 86 .RE 95 87 .PP 96 88 gid=\fIarg\fR 97 .RS 3n98 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.89 .RS 4 90 sets the gid that will own all files on the mounted filesystem\. It may be specified as either a groupname or a numeric gid\. For other considerations see the description of uid above\. 99 91 .RE 100 92 .PP 101 93 port=\fIarg\fR 102 .RS 3n 103 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. 94 .RS 4 95 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\. 96 .RE 97 .PP 98 servern=\fIarg\fR 99 .RS 4 100 Specify the server netbios name (RFC1001 name) to use when attempting to setup a session to the server\. Although rarely needed for mounting to newer servers, this option is needed for mounting to some older servers (such as OS/2 or Windows 98 and Windows ME) since when connecting over port 139 they, unlike most newer servers, do not support a default server name\. A server name can be up to 15 characters long and is usually uppercased\. 104 101 .RE 105 102 .PP 106 103 netbiosname=\fIarg\fR 107 .RS 3n108 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 .104 .RS 4 105 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\. 109 106 .RE 110 107 .PP 111 108 file_mode=\fIarg\fR 112 .RS 3n113 If the server does not support the CIFS Unix extensions this overrides the default file mode .109 .RS 4 110 If the server does not support the CIFS Unix extensions this overrides the default file mode\. 114 111 .RE 115 112 .PP 116 113 dir_mode=\fIarg\fR 117 .RS 3n118 If the server does not support the CIFS Unix extensions this overrides the default mode for directories .114 .RS 4 115 If the server does not support the CIFS Unix extensions this overrides the default mode for directories\. 119 116 .RE 120 117 .PP 121 118 ip=\fIarg\fR 122 .RS 3n123 sets the destination host or IP address.119 .RS 4 120 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\. 124 121 .RE 125 122 .PP 126 123 domain=\fIarg\fR 127 .RS 3n124 .RS 4 128 125 sets the domain (workgroup) of the user 129 126 .RE 130 127 .PP 131 128 guest 132 .RS 3n133 don 't prompt for a password129 .RS 4 130 don\'t prompt for a password 134 131 .RE 135 132 .PP 136 133 iocharset 137 .RS 3n138 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.134 .RS 4 135 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\. 139 136 .RE 140 137 .PP 141 138 ro 142 .RS 3n143 mount read -only139 .RS 4 140 mount read\-only 144 141 .RE 145 142 .PP 146 143 rw 147 .RS 3n148 mount read -write144 .RS 4 145 mount read\-write 149 146 .RE 150 147 .PP 151 148 setuids 152 .RS 3n153 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).149 .RS 4 150 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)\. 154 151 .RE 155 152 .PP 156 153 nosetuids 157 .RS 3n158 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.154 .RS 4 155 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\. 159 156 .RE 160 157 .PP 161 158 perm 162 .RS 3n163 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.159 .RS 4 160 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\. 164 161 .RE 165 162 .PP 166 163 noperm 167 .RS 3n168 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).164 .RS 4 165 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)\. 169 166 .RE 170 167 .PP 171 168 directio 172 .RS 3n173 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.169 .RS 4 170 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\. 174 171 .RE 175 172 .PP 176 173 mapchars 177 .RS 3n178 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.174 .RS 4 175 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\. 179 176 .RE 180 177 .PP 181 178 nomapchars 182 .RS 3n179 .RS 4 183 180 Do not translate any of these seven characters (default) 184 181 .RE 185 182 .PP 186 183 intr 187 .RS 3n184 .RS 4 188 185 currently unimplemented 189 186 .RE 190 187 .PP 191 188 nointr 192 .RS 3n189 .RS 4 193 190 (default) currently unimplemented 194 191 .RE 195 192 .PP 196 193 hard 197 .RS 3n198 The program accessing a file on the cifs mounted file system will hang when the server crashes .194 .RS 4 195 The program accessing a file on the cifs mounted file system will hang when the server crashes\. 199 196 .RE 200 197 .PP 201 198 soft 202 .RS 3n203 (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 .199 .RS 4 200 (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 201 .RE 205 202 .PP 206 203 noacl 207 .RS 3n208 Do not allow POSIX ACL operations even if server would support them .209 .sp 210 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.204 .RS 4 205 Do not allow POSIX ACL operations even if server would support them\. 206 .sp 207 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\. 211 208 .RE 212 209 .PP 213 210 nocase 214 .RS 3n215 Request case insensitive path name matching (case sensitive is the default if the server suports it) .211 .RS 4 212 Request case insensitive path name matching (case sensitive is the default if the server suports it)\. 216 213 .RE 217 214 .PP 218 215 sec= 219 .RS 3n 220 Security mode. Allowed values are: 221 .RS 3n 222 .TP 3n 223 \(bu 216 .RS 4 217 Security mode\. Allowed values are: 218 .sp 219 .RS 4 220 .ie n \{\ 221 \h'-04'\(bu\h'+03'\c 222 .\} 223 .el \{\ 224 .sp -1 225 .IP \(bu 2.3 226 .\} 224 227 none attempt to connection as a null user (no name) 225 .TP 3n 226 \(bu 228 .RE 229 .sp 230 .RS 4 231 .ie n \{\ 232 \h'-04'\(bu\h'+03'\c 233 .\} 234 .el \{\ 235 .sp -1 236 .IP \(bu 2.3 237 .\} 227 238 krb5 Use Kerberos version 5 authentication 228 .TP 3n 229 \(bu 239 .RE 240 .sp 241 .RS 4 242 .ie n \{\ 243 \h'-04'\(bu\h'+03'\c 244 .\} 245 .el \{\ 246 .sp -1 247 .IP \(bu 2.3 248 .\} 230 249 krb5i Use Kerberos authentication and packet signing 231 .TP 3n 232 \(bu 250 .RE 251 .sp 252 .RS 4 253 .ie n \{\ 254 \h'-04'\(bu\h'+03'\c 255 .\} 256 .el \{\ 257 .sp -1 258 .IP \(bu 2.3 259 .\} 233 260 ntlm Use NTLM password hashing (default) 234 .TP 3n 235 \(bu 261 .RE 262 .sp 263 .RS 4 264 .ie n \{\ 265 \h'-04'\(bu\h'+03'\c 266 .\} 267 .el \{\ 268 .sp -1 269 .IP \(bu 2.3 270 .\} 236 271 ntlmi 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 \(bu 272 .RE 273 .sp 274 .RS 4 275 .ie n \{\ 276 \h'-04'\(bu\h'+03'\c 277 .\} 278 .el \{\ 279 .sp -1 280 .IP \(bu 2.3 281 .\} 239 282 ntlmv2 Use NTLMv2 password hashing 240 .TP 3n 241 \(bu 283 .RE 284 .sp 285 .RS 4 286 .ie n \{\ 287 \h'-04'\(bu\h'+03'\c 288 .\} 289 .el \{\ 290 .sp -1 291 .IP \(bu 2.3 292 .\} 242 293 ntlmv2i Use NTLMv2 password hashing with packet signing 243 . RE244 . IP "" 3n245 [NB This [sec parameter] is under development and expected to be available in cifs kernel module 1 .40 and later]294 .sp 295 .RE 296 [NB This [sec parameter] is under development and expected to be available in cifs kernel module 1\.40 and later] 246 297 .RE 247 298 .PP 248 299 nobrl 249 .RS 3n250 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).300 .RS 4 301 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)\. 251 302 .RE 252 303 .PP 253 304 sfu 254 .RS 3n255 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.305 .RS 4 306 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\. 256 307 .RE 257 308 .PP 258 309 serverino 259 .RS 3n260 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.310 .RS 4 311 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\. 261 312 .RE 262 313 .PP 263 314 noserverino 264 .RS 3n265 client generates inode numbers (rather than using the actual one from the server) by default .315 .RS 4 316 client generates inode numbers (rather than using the actual one from the server) by default\. 266 317 .RE 267 318 .PP 268 319 nouser_xattr 269 .RS 3n270 (default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise .320 .RS 4 321 (default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise\. 271 322 .RE 272 323 .PP 273 324 rsize=\fIarg\fR 274 .RS 3n275 default network read size 325 .RS 4 326 default network read size (usually 16K)\. The client currently can not use rsize larger than CIFSMaxBufSize\. CIFSMaxBufSize defaults to 16K and may be changed (from 8K to the maximum kmalloc size allowed by your kernel) at module install time for cifs\.ko\. Setting CIFSMaxBufSize to a very large value will cause cifs to use more memory and may reduce performance in some cases\. To use rsize greater than 127K (the original cifs protocol maximum) also requires that the server support a new Unix Capability flag (for very large read) which some newer servers (e\.g\. Samba 3\.0\.26 or later) do\. rsize can be set from a minimum of 2048 to a maximum of 130048 (127K or CIFSMaxBufSize, whichever is smaller) 276 327 .RE 277 328 .PP 278 329 wsize=\fIarg\fR 279 .RS 3n 280 default network write size 281 .RE 282 .PP 283 --verbose 284 .RS 3n 285 Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example: 286 .sp 287 mount -t cifs //server/share /mnt --verbose -o user=username 288 .RE 330 .RS 4 331 default network write size (default 57344) maximum wsize currently allowed by CIFS is 57344 (fourteen 4096 byte pages) 332 .RE 333 .PP 334 \-\-verbose 335 .RS 4 336 Print additional debugging information for the mount\. Note that this parameter must be specified before the \-o\. For example: 337 .sp 338 mount \-t cifs //server/share /mnt \-\-verbose \-o user=username 339 .RE 340 .SH "SERVICE FORMATTING AND DELIMITERS" 341 .PP 342 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 (\e) 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\. 343 .PP 344 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\. 289 345 .SH "ENVIRONMENT VARIABLES" 290 346 .PP 291 347 The variable 292 \f BUSER\fR293 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.348 \fIUSER\fR 349 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\. 294 350 .PP 295 351 The variable 296 \f BPASSWD\fR297 may contain the password of the person using the client .352 \fIPASSWD\fR 353 may contain the password of the person using the client\. 298 354 .PP 299 355 The variable 300 \f BPASSWD_FILE\fR301 may contain the pathname of a file to read the password from . A single line of input is read and used as the password.356 \fIPASSWD_FILE\fR 357 may contain the pathname of a file to read the password from\. A single line of input is read and used as the password\. 302 358 .SH "NOTES" 303 359 .PP 304 This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled .360 This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled\. 305 361 .SH "CONFIGURATION" 306 362 .PP 307 The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem . In the directory363 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 308 364 \fI/proc/fs/cifs\fR 309 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 file310 \fIfs/cifs/README\fR .365 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 366 \fIfs/cifs/README\fR\. 311 367 .SH "BUGS" 312 368 .PP 313 Mounting using the CIFS URL specification is currently not supported .314 .PP 315 The credentials file does not handle usernames or passwords with leading space .316 .PP 317 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.369 Mounting using the CIFS URL specification is currently not supported\. 370 .PP 371 The credentials file does not handle usernames or passwords with leading space\. 372 .PP 373 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\. 318 374 .SH "VERSION" 319 375 .PP 320 This man page is correct for version 1 .39 of the cifs vfs filesystem (roughly Linux kernel 2.6.15).376 This man page is correct for version 1\.52 of the cifs vfs filesystem (roughly Linux kernel 2\.6\.24)\. 321 377 .SH "SEE ALSO" 322 378 .PP 323 Documentation/filesystems/cifs .txt and fs/cifs/README in the linux kernel source tree may contain additional options and information.379 Documentation/filesystems/cifs\.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information\. 324 380 .PP 325 381 \fBumount.cifs\fR(8) … … 328 384 Steve French 329 385 .PP 330 The syntax and manpage were loosely based on that of smbmount . It was converted to Docbook/XML by Jelmer Vernooij.386 The syntax and manpage were loosely based on that of smbmount\. It was converted to Docbook/XML by Jelmer Vernooij\. 331 387 .PP 332 388 The maintainer of the Linux cifs vfs and the userspace tool 333 \f Bmount.cifs\fR389 \fImount\.cifs\fR 334 390 is 335 Steve French . The391 Steve French\. The 336 392 Linux CIFS Mailing list 337 is the preferred place to ask questions regarding these programs. 338 393 is the preferred place to ask questions regarding these programs\.
Note:
See TracChangeset
for help on using the changeset viewer.
