umask
even if default ACLs are present. (Keep in mind that it is the
version of the receiving rsync that affects these behaviors.)
--executability, -E
This option causes rsync to preserve the executability (or non‐
executability) of regular files when --perms is not enabled. A
regular file is considered to be executable if at least one ’x’
is turned on in its permissions. When an existing destination
file’s executability differs from that of the corresponding
source file, rsync modifies the destination file’s permissions as
follows:
o To make a file non‐executable, rsync turns off all its ’x’
permissions.
o To make a file executable, rsync turns on each ’x’ permis‐
sion that has a corresponding ’r’ permission enabled.
If --perms is enabled, this option is ignored.
--acls, -A
This option causes rsync to update the destination ACLs to be the
same as the source ACLs. The option also implies --perms.
The source and destination systems must have compatible ACL en‐
tries for this option to work properly. See the --fake‐super op‐
tion for a way to backup and restore ACLs that are not compati‐
ble.
--xattrs, -X
This option causes rsync to update the destination extended at‐
tributes to be the same as the source ones.
For systems that support extended‐attribute namespaces, a copy
being done by a super‐user copies all namespaces except system.*.
A normal user only copies the user.* namespace. To be able to
backup and restore non‐user namespaces as a normal user, see the
--fake‐super option.
The above name filtering can be overridden by using one or more
filter options with the x modifier. When you specify an xattr‐
affecting filter rule, rsync requires that you do your own sys‐
tem/user filtering, as well as any additional filtering for what
xattr names are copied and what names are allowed to be deleted.
For example, to skip the system namespace, you could specify:
‐‐filter=’‐x system.*’
To skip all namespaces except the user namespace, you could spec‐
ify a negated‐user match:
‐‐filter=’‐x! user.*’
To prevent any attributes from being deleted, you could specify a
receiver‐only rule that excludes all names:
‐‐filter=’‐xr *’
Note that the -X option does not copy rsync’s special xattr val‐
ues (e.g. those used by --fake‐super) unless you repeat the op‐
tion (e.g. -XX). This "copy all xattrs" mode cannot be used with
--fake‐super.
--chmod=CHMOD
This option tells rsync to apply one or more comma‐separated
"chmod" modes to the permission of the files in the transfer.
The resulting value is treated as though it were the permissions
that the sending side supplied for the file, which means that
this option can seem to have no effect on existing files if
--perms is not enabled.
In addition to the normal parsing rules specified in the chmod(1)
manpage, you can specify an item that should only apply to a di‐
rectory by prefixing it with a ’D’, or specify an item that
should only apply to a file by prefixing it with a ’F’. For ex‐
ample, the following will ensure that all directories get marked
set‐gid, that no files are