On Thu, Jun 08, 2017 at 07:09:24AM +0000, just subscribed for rsync-qa from
bugzilla via rsync wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=12806
>
> --- Comment #4 from Heinz-Willi Wyes <[email protected]> ---
> I got a personal message from Lars Ellenberg that went also to
> [email protected] and [email protected]. He wrote:
>
> ------------------
> Calling chmod only on (optimization: non-empty) directories would fix this.
> I don't need to chmod a *file* before unlinking it, I just need write
> permission on the directory it is located in.
>
> (Now you have to convince the "appliance" to use a patched rsync ...)
Note that as long as you have only files (not directories) without write
permissions, you can potentially work around this using "--super" (or
"--fake-super"),
because in that case rsync sets "am_root" to 2 (or -1),
"!am_root" becomes false in the various conditions,
and the do_chmod() will not even be called.
Not sure though what other implications --[fake-]super will have for your
usecase.
Lars Ellenberg
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
