Yohoo!
I'm using rsnapshot-1.3.0-1.el5.rf (from DAG) and rsync-2.6.9-1.el5.rf (from CentOS5) together.
Rsnapshot now starts every task with the "--relative" switch. Without this switch it will backup all subsequent folders (like /proc and so on) which isn't desired. So I can't omit the "--relative".
But there was a bug for rsync prior to 2.6.9 that it won't delete files from the destination directory when "--relative" and "--delete" are used together. See at http://samba.anu.edu.au/ftp/rsync/rsync-2.6.9-NEWS for this.
Now I figured out that this bug is fixed in FedoraCore5. See http://www.redhat.com/archives/fedora-package-announce/2007-February/msg0010... .html The version there is rsync-2.6.9-1.FC5.1.
In CentOS5 I have rsync-2.6.9-1.el5.rf
Now my question is if this bug is fixed in CentOS5/ RHEL5?
If not, is there something scheduled to fix it or should I build the rsync package from the source of the FC5 tree?
Thanks!
Christian Volker
Technical Support Engineer
Christian Volker wrote:
Yohoo!
I'm using rsnapshot-1.3.0-1.el5.rf (from DAG) and rsync-2.6.9-1.el5.rf (from CentOS5) together.
Rsnapshot now starts every task with the "--relative" switch. Without this switch it will backup all subsequent folders (like /proc and so on) which isn't desired. So I can't omit the "--relative".
But there was a bug for rsync prior to 2.6.9 that it won't delete files from the destination directory when "--relative" and "--delete" are used together. See at http://samba.anu.edu.au/ftp/rsync/rsync-2.6.9-NEWS for this.
Now I figured out that this bug is fixed in FedoraCore5. See http://www.redhat.com/archives/fedora-package-announce/2007-February/msg0010... .html The version there is rsync-2.6.9-1.FC5.1.
In CentOS5 I have rsync-2.6.9-1.el5.rf
Now my question is if this bug is fixed in CentOS5/ RHEL5?
If not, is there something scheduled to fix it or should I build the rsync package from the source of the FC5 tree?
Thanks!
Christian Volker
I am not sure if it is fixed in CentOS-5 or not, but that is not relevant since you are NOT using the CentOS-5 rsync.
rsync-2.6.9-1.el5.rf ... the rf stands for RPMForge .. so, that is the RPMForge version of rsync.
rsync-2.6.8-3.1 <== that is the version of rsync from CentOS-5.
Yohoo!
In CentOS5 I have rsync-2.6.9-1.el5.rf Now my question is if this bug is fixed in CentOS5/ RHEL5?
I am not sure if it is fixed in CentOS-5 or not, but that is not relevant since you are NOT using the CentOS-5 rsync.
rsync-2.6.9-1.el5.rf ... the rf stands for RPMForge .. so, that is the RPMForge version of rsync.
rsync-2.6.8-3.1 <== that is the version of rsync from CentOS-5.
You're right! I wasn't aware that this is the version from RPMForge. On the source server there was still the CentOS one 2.6.8 WITH the bug.
So the solution is:
Original rsync-2.6.8-3.1 has still this bug. DAG rsync-2.6.9-1.el5.rf has fixed this bug.
With the newer version on both sides it now works fine!
Thanks for the hint.
Christian Volker Technical Support Engineer
---------------------------------------- Ballincollig, Co. Cork Ireland