rsync - Mar 2020 - Would you expect --perms -M--fake-super to set the file mode to the original one?

Thank you for the feedback, I'm glad to see that different people see the 
issue
differently. As a followup question, what would you expect this to do:

rsync --perms --chmod g+rX -M--fake-super src dst

I would expect it to store the original permissions in the xattr, while
modifying the real file mode according to the chmod.

On Thursday, March 12, 2020 6:06:34 PM CET, Kevin Korb via rsync
wrote:
> Permissions don't require super.  Any place where permissions can't
be
> stored certainly can't handle xattrs either.  So, I wouldn't expect
> --fake-super to affect --perms at all.
>
> On 3/12/20 12:46 PM, Dimitrios Apostolou via rsync wrote:
>> rsync --perms -M--fake-super src dst
>> 
>> For me, this command means that rsync should save the original 
>> perms in the
>> xattr, and leave the real file mode to the umask default. 
>> Currently it also
>> modifies the real file mode, and there is no way to store something
>> different ...
>

I would expect that the sending rsync would only send the perms provided
modified by the --chmod.  I wouldn't expect the receiver to even know
the other permissions.

On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote:
> Thank you for the feedback, I'm glad to see that different people see
> the issue
> differently. As a followup question, what would you expect this to do:
> 
> rsync --perms --chmod g+rX -M--fake-super src dst
> 
> I would expect it to store the original permissions in the xattr, while
> modifying the real file mode according to the chmod.
> 
> On Thursday, March 12, 2020 6:06:34 PM CET, Kevin Korb via rsync wrote:
>> Permissions don't require super.? Any place where permissions
can't be
>> stored certainly can't handle xattrs either.? So, I wouldn't
expect
>> --fake-super to affect --perms at all.
>>
>> On 3/12/20 12:46 PM, Dimitrios Apostolou via rsync wrote:
>>> rsync --perms -M--fake-super src dst
>>>
>>> For me, this command means that rsync should save the original
perms
>>> in the
>>> xattr, and leave the real file mode to the umask default. Currently
>>> it also
>>> modifies the real file mode, and there is no way to store something
>>> different ...
>>
> 
> 
-- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			https://sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20200312/8a2a93ef/signature.sig>

Thanks. This is a bit counter-intuitive to me. So how would you tell
rsync to store the original permissions in the xattr, but do not touch
the real file mode?

On Thursday, March 12, 2020 6:26:18 PM CET, Kevin Korb via rsync
wrote:
> I would expect that the sending rsync would only send the perms provided
> modified by the --chmod.  I wouldn't expect the receiver to even know
> the other permissions.
>
> On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote:
>> Thank you for the feedback, I'm glad to see that different people
see
>> the issue
>> differently. As a followup question, what would you expect this to do:
>> 
>> rsync --perms --chmod g+rX -M--fake-super src dst
>> 
>> I would expect it to store the original permissions in the 
>> xattr, while ...
>