summaryrefslogtreecommitdiff
path: root/mount.cifs.8
diff options
context:
space:
mode:
authorJeff Layton <jlayton@samba.org>2011-10-19 14:18:12 -0400
committerJeff Layton <jlayton@samba.org>2011-10-19 14:18:12 -0400
commite92709981e5d3e927a0ba823d7c94d7cf0940897 (patch)
tree5250fa01de4a456c93a04da6ff1748a7f96ea41f /mount.cifs.8
parentc55ad41d1a11e897b4db166f800d4abd71d86652 (diff)
downloadcifs-utils-e92709981e5d3e927a0ba823d7c94d7cf0940897.tar.gz
cifs-utils-e92709981e5d3e927a0ba823d7c94d7cf0940897.tar.bz2
cifs-utils-e92709981e5d3e927a0ba823d7c94d7cf0940897.zip
manpage: cleanups to new backupuid/gid sections
Minor cleanups and consistency fixes... Cc: Shirish Pargaonkar <shirishpargaonkar@gmail.com> Signed-off-by: Jeff Layton <jlayton@samba.org>
Diffstat (limited to 'mount.cifs.8')
-rw-r--r--mount.cifs.814
1 files changed, 5 insertions, 9 deletions
diff --git a/mount.cifs.8 b/mount.cifs.8
index 8207bcb..958efa5 100644
--- a/mount.cifs.8
+++ b/mount.cifs.8
@@ -282,16 +282,16 @@ See sections on
for more information\&.
.RE
.PP
-backupuid=arg
+backupuid=\fIarg\fR
.RS 4
-Restrict access to files, with the backup intent, to a user. Either a name or an id must be provided as an argument, there are no default values.
+Restrict access to files with the backup intent to a user. Either a name or an id must be provided as an argument, there are no default values.
.sp
See section \fIACCESSING FILES WITH BACKUP INTENT\fR for more details
.RE
.PP
-backupgid=arg
+backupgid=\fIarg\fR
.RS 4
-Restrict Allow access to files, with the backup intent, to a group. Either a name or an id must be provided as an argument, there are no default values.
+Restrict access to files with the backup intent to a group. Either a name or an id must be provided as an argument, there are no default values.
.sp
See section \fIACCESSING FILES WITH BACKUP INTENT\fR for more details
.RE
@@ -625,11 +625,7 @@ But the user testuser, if it becomes part of the group Backup Operators, can ope
Any user on the client side who can authenticate as such a user on the server,
can access the files with the backup intent. But it is desirable and preferable for security reasons amongst many, to restrict this special right.
-The mount option backupuid is used to restrict this special right to a user which is specified by either a name or an id.
-.sp 0
-The mount option backupgid is used to restrict this special right to the users in a group which is specified by either a name or an id.
-.sp 0
-These two mount options can be used together.
+The mount option backupuid is used to restrict this special right to a user which is specified by either a name or an id. The mount option backupgid is used to restrict this special right to the users in a group which is specified by either a name or an id. These two mount options can be used together.
.SH "FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS"
.PP
The core CIFS protocol does not provide unix ownership information or mode for files and directories\&. Because of this, files and directories will generally appear to be owned by whatever values the uid= or gid= options are set, and will have permissions set to the default file_mode and dir_mode for the mount\&. Attempting to change these values via chmod/chown will return success but have no effect\&.