Date: Tue, 12 Apr 2016 08:49:36 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: rsync update mixed environment Message-ID: <570CA890.7090706@FreeBSD.org> In-Reply-To: <570C9DE3.6030601@parts-unknown.org> References: <570C9DE3.6030601@parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--LS4BCQqBWHQU2W9nn8GWaRH97TBn12mSp
Content-Type: multipart/mixed; boundary="P2npk1A6dh76ilPqRbSNXXfN7JaAUOs5F"
From: Matthew Seaman <matthew@FreeBSD.org>
To: freebsd-questions@freebsd.org
Message-ID: <570CA890.7090706@FreeBSD.org>
Subject: Re: rsync update mixed environment
References: <570C9DE3.6030601@parts-unknown.org>
In-Reply-To: <570C9DE3.6030601@parts-unknown.org>
--P2npk1A6dh76ilPqRbSNXXfN7JaAUOs5F
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
On 12/04/2016 08:04, David Benfell wrote:
> I'm used to rsync from Linux, where one can do rsync -auvz to update th=
e
> files from one directory to another between networked systems.
>=20
> The z option gave me trouble in FreeBSD but I guess you can do zz
> instead. I guess I missed a memo on whatever is going on with this.
The FreeBSD port is using the zlib from the base system rather than what
is bundled with rsync. This does have an effect on functionality,
particularly on interoperability with other versions of rsync. If
you're using rsync in a diverse environment, it might be an idea to
toggle that option setting in the rsync port and reinstall it.
> Either way, updates don't seem to happen reliably when I do this from a=
> Linux system to a FreeBSD system. The failure is silent; it just doesn'=
t
> seem to recognize that a file in the source is newer than the version i=
n
> the destination. And then I wonder why an updated file didn't propagate=
=2E
Curious. Is there any problem going in the other direction? FreeBSD to
Linux? What are the versions of rsync on either side? Does using
compression or not affect the reliability? (ie. try your rsync without
any compression at all.) I'm thinking this could be a problem due to
the change in the way the compression option works with different
rsync(1) versions. Quoting the man page:
This matching-data com-
pression comes at a cost of CPU, though, and can be disabled by
repeating the -z option, but only if both sides are at least
version 3.1.1.
Cheers,
Matthew
--P2npk1A6dh76ilPqRbSNXXfN7JaAUOs5F--
--LS4BCQqBWHQU2W9nn8GWaRH97TBn12mSp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQJ8BAEBCgBmBQJXDKiWXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC
QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT8CcP/RijjB+OEvAPloMb8lEjh7d/
6xdMUiTUN8c33i8ln7GNKkaNwOX7v2rFoGzUitAIyzXCyTnbF6TqhJoTqcVkqq3J
AbSQnM1+oZ1NPlGdK5F55aOiZPZH4E6pKsjCBll+9xDA7fxteTC5jQug+fix2R75
n0vO+b79FdQhPFthtQGEHbAadJ53VrSLcS1SH3NnleVThEPrvwFLyPHHCQ2UDOq+
W7BUluMWJaCCcfmp+x651H99dytOmD1D5MujEXLw55lM6PQlAinVt3erKnW/+8hz
MOKJPfTVc+6SoSmZ2yEGd28wkiCkw8izKN5y8WfxbA7iIHenlNWqCelCCfyUiQHV
5vF9yGfyDyLPLjSN6bBGSVXEikPeR43fhJuvFTa9i0KXNWvkKwPfUYZbeTERD3SZ
F26cOKXcp7rGTKw+V7BkuLHFm6cuku8c0cPfL6i6AIQUqNhKdVTOy2RH69gIaMi0
5BBAT7yglPMCzVWk6GqfEWrzm18ytqtGHeVI1pVwk4hnW0D9+1d1Xs4zg9hpQepM
3Fo/sOTFRCXpTr6ILUy19UwvbP+5f9/s4uq/mQYg7/a+IDqcHHTJBnnDuYZS6Rl+
exwPwBPciQpB3KEFmRj688572bnNuJ2Rjaxi9OBFpZPZAau36hQ2up18upI9m7AB
sPnIl5ueP7wyTRjbb2e8
=cGMz
-----END PGP SIGNATURE-----
--LS4BCQqBWHQU2W9nn8GWaRH97TBn12mSp--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?570CA890.7090706>