We have a rsync'd filesystem which generally contains very large files that only
grow.
We've specifically used the --append option to handle these files - since
otherwise rsync is effectively CPU bound the whole time.
I'd always assumed that any files that were simply modified (without a change
Hi Ram,
yes, this is only an issue with certain font types, not all fonts put the
font information in the resource fork.
This is not an issue with rsync, but related to how you copied the data.
CarbonCopyCloner uses rsync itself, so I’d be surprised if it’s
substantially slower.
Regards
Hi Bryan,
thanks for your kind reply but it happend only with some fonts not all font
file, (email with attachment is under verification by admin, so i resend this
without attachment file) here i attach 2 screenshot one original folder and
second backup folder, you can notice that the font .otf