From: Wayne Davison <wayne@opencoder.net>
To: cygwin@kosowsky.org
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: 'rsync -a' not preserving ownership
Date: Mon, 3 Jan 2022 21:23:28 -0800 [thread overview]
Message-ID: <CAHSx_Sttb5OWFZyXULttAjADTf9AaygBxd5kaZ=7m8Xwrr3eOA@mail.gmail.com> (raw)
In-Reply-To: <25043.8585.322210.817972@consult.pretender>
On Mon, Jan 3, 2022 at 8:17 AM <cygwin@kosowsky.org> wrote:
> So, why is 'cp -a' able to preserve ownership while 'rsync -a' fails
> and sets ownership to the login name?
Rsync is rather old-school Unix-oriented, so it only checks if its uid
is 0 to see if it should try to chown things. You can give it the
--super option to tell it to try root things when you're a non-0 user,
which works in my testing.
..wayne..
prev parent reply other threads:[~2022-01-04 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:17 cygwin
2022-01-04 5:23 ` Wayne Davison [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHSx_Sttb5OWFZyXULttAjADTf9AaygBxd5kaZ=7m8Xwrr3eOA@mail.gmail.com' \
--to=wayne@opencoder.net \
--cc=cygwin@cygwin.com \
--cc=cygwin@kosowsky.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).