Changeset 221 for branches/samba-3.3.x/docs/manpages/mount.cifs.8

Timestamp:

May 24, 2009, 7:17:10 AM (16 years ago)

Author:

Herwig Bauernfeind

Message:

Update Samba 3.3 to 3.3.1

File:

• branches/samba-3.3.x/docs/manpages/mount.cifs.8 (modified) (4 diffs)

branches/samba-3.3.x/docs/manpages/mount.cifs.8

@@ -2 +2 @@
 .\"    Author: [see the "AUTHOR" section]
 .\" Generator: DocBook XSL Stylesheets v1.74.0 <http://docbook.sf.net/>
-.\"      Date: 01/27/2009
+.\"      Date: 02/24/2009
 .\"    Manual: System Administration tools
 .\"    Source: Samba 3.3
 .\"  Language: English
 .\"
-.TH "MOUNT\&.CIFS" "8" "01/27/2009" "Samba 3\&.3" "System Administration tools"
+.TH "MOUNT\&.CIFS" "8" "02/24/2009" "Samba 3\&.3" "System Administration tools"
 .\" -----------------------------------------------------------------
 .\" * (re)Define some macros
@@ -184 +184 @@
 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\&.
 .PP
-The mount\&.cifs utility attaches the UNC name (exported network resource) to the local directory
+The mount\&.cifs utility attaches the UNC name (exported network resource) specified as
+\fIservice\fR
+(using //server/share syntax, where "server" is the server name or IP address and "share" is the name of the share) to the local directory
 \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\&.
 .PP
@@ -271 +273 @@
 uid=\fIarg\fR
 .RS 4
-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\&.
+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 specified 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\&.
 .RE
 .PP
@@ -393 +395 @@
 Do not allow POSIX ACL operations even if server would support them\&.
 .sp
-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\&.
+The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers version 3\&.0\&.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 basis by specifying "noacl" on mount\&.
 .RE
 .PP