Bug 171935 - Update rsync to >= 2.6.4
Update rsync to >= 2.6.4
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rsync (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Simo Sorce
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-10-27 17:57 EDT by Terje Bless
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-16 10:16:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Terje Bless 2005-10-27 17:57:37 EDT
For a (large, critical) RHEL4 installation, we have need of the
"--remove-sent-files" option which was introduced in rsync 2.6.4.

Please consider updating the RHEL4 rsync to 2.6.4 or newer -- 2.6.6 is
latest, and 2.6.5/.6 contain many other relevant bug fixes and efficiency
enhancements -- for U3.

The Dag packages are currently based on rsync 2.6.6 and appear to work
fine in our testing (it's what we're running while waiting for official
packages from RH).
Comment 1 Dean Eckstrom 2006-02-22 09:30:43 EST
There is a bug in versions < 2.6.4 related to compression (-z) and transfers of
large files (>4GB).   Rsyncing directories with large files may randomly fail,
based on the actual file 'contents'.  see:

I can repeatable produce the error mentioned in bugzilla report on current
RedHat AS4.

v. 2.6.4 is available in the Fedora Core4 release, but has not made it way into
AS4 distribution.  Considering the degree rsync is widely relied upon, and
assumed to be bug free... I would urgently suggest pushing a new version on into
RedHat Updates.
Comment 2 Simo Sorce 2007-02-16 10:16:19 EST
We usually don't do version upgrades in RHEL.
If you need a new feature, contact your support person to open a bug to ask for
this specific feature backported.

Note You need to log in before you can comment on or make changes to this bug.