rsync-3.1.0 --chown, --usermap, and --groupmap ignored?
jed at 59A2.org
Mon Oct 14 08:46:47 MDT 2013
Paul Slootman <paul+rsync at wurtel.net> writes:
> No, because you're not running the rsync command as the superuser,
> and not using the --owner / --group options.
Thanks, adding --group works, and --owner --super is sufficient to
generate an error when attempting to change the user permissions. I
would suggest that the docs for --chown would do well to mention that
--owner (--super) and --group are needed in order to have the effect
stated in the first sentence.
This option forces all files to be owned by USER with group
GROUP. This is a simpler interface than using --usermap and
--groupmap directly, but it is implemented using those options
internally, so you cannot mix them. If either the USER or GROUP
is empty, no mapping for the omitted user/group will occur. If
GROUP is empty, the trailing colon may be omitted, but if USER is
empty, a leading colon must be supplied.
If you specify "--chown=foo:bar, this is exactly the same as
specifying "--usermap=*:foo --groupmap=*:bar", only easier.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available
More information about the rsync