Thanks Kevin.
I tried leaving off --fileflags and got entirely different error output:
rsync: [generator] failed to set file flags on
"/Users/redacted/Library/Accounts": Operation not permitted (1)
In this example, the Library subdir on the source has the "hidden" flag
set; my understanding of t
No, rsync normally handles such problems well. Unfortunately,
--fileflags is an OS vendor added feature rather than an official rsync
feature so it is less well thought out.
On 10/31/21 3:51 AM, Perry Hutchison wrote:
> That sort of snafu is why find(1) has the -depth directive.
> Does rsync have
That sort of snafu is why find(1) has the -depth directive.
Does rsync have anything similar?
Kevin Korb via rsync wrote:
> There maybe a proper solution but an obvious workaround would be to run
> rsync twice. The first time without the --fileflags option.
>
> --no-perms wouldn't help. That i
There maybe a proper solution but an obvious workaround would be to run
rsync twice. The first time without the --fileflags option.
--no-perms wouldn't help. That is only the standard unix permissions.
On 10/30/21 8:04 PM, Fred Fugate via rsync wrote:
> Hi,
>
> I have some subdirectories withi
Hi,
I have some subdirectories within a home directory that are chflagged schg,
aka system immutable.
When I rsync the home directory to another machine, I get lots of errors
for these subdirectories and they fail to copy to the target. NOTE: The
target is empty; rsync is copying to an empty remo