[PATCH] mount.cifs.8: Change "owenrship" to "ownership"

Wieland Hoffmann themineo at gmail.com
Wed Nov 13 03:18:31 MST 2013


Signed-off-by: Wieland Hoffmann <themineo at gmail.com>
---
 mount.cifs.8 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mount.cifs.8 b/mount.cifs.8
index 2643145..212774d 100644
--- a/mount.cifs.8
+++ b/mount.cifs.8
@@ -748,7 +748,7 @@ If either upcall to cifs.idmap is not setup correctly or winbind is not configur
 .RE
 .SH "ACCESSING FILES WITH BACKUP INTENT"
 .PP
-For an user on the server, desired access to a file is determined by the permissions and rights associated with that file.  This is typically accomplished using owenrship and ACL.  For a user who does not have access rights to a file, it is still possible to access that file for a specific or a targeted purpose by granting special rights.  One of the specific purposes is to access a file with the intent to either backup or restore i.e. backup intent.  The right to access a file with the backup intent can typically be granted by making that user a part of the built-in group Backup Operators.  Thus, when this user attempts to open a file with the backup intent, open request is sent by setting the bit FILE_OPEN_FOR_BACKUP_INTENT as one of the CreateOptions.
+For an user on the server, desired access to a file is determined by the permissions and rights associated with that file.  This is typically accomplished using ownership and ACL.  For a user who does not have access rights to a file, it is still possible to access that file for a specific or a targeted purpose by granting special rights.  One of the specific purposes is to access a file with the intent to either backup or restore i.e. backup intent.  The right to access a file with the backup intent can typically be granted by making that user a part of the built-in group Backup Operators.  Thus, when this user attempts to open a file with the backup intent, open request is sent by setting the bit FILE_OPEN_FOR_BACKUP_INTENT as one of the CreateOptions.
 
 As an example, on a Windows server, a user named testuser, cannot open this file with such a security descriptor.
 .PP
-- 
1.8.4.2



More information about the samba-technical mailing list