Thanks Wayne! Both options worked well -- upgrading clients to 2.6.0 or using /. instead of / to specify the root directory.
Perhaps a recap for the regulars here, but maybe useful to some -- I found that I only needed to upgrade to 2.6.0 on the remote/source side. Upgrading to 2.6.0 on my backup server without upgrading the remote side did not have the desired effect. I couldn't find an RPM version of rsync-2.6.0 for Redhat 7.2 so I created one. It works well on my RH 7.2 and 7.3 hosts. Do you want it? Possibly to include in http://rsync.samba.org/ftp/rsync/binaries/redhat? Thought that might be a small opportunity for me to give back to the project. I could create the RPM for 2.6.1 when it is released too. -Brian On Wed, 21 Apr 2004, Wayne Davison wrote: > On Wed, Apr 21, 2004 at 04:59:19PM -0400, Brian McEntire wrote: > > rsync -av -e ssh --one-file-system --numeric-ids --relative --delete > > --exclude-from=/backups/control/all.exclude '[EMAIL PROTECTED]:/ /boot /dev/shm > > /sandbox ' /backups/A > > You have a couple choices on how to make this work: > > - Upgrade to at least 2.6.0 -- it fixes this bug with the --relative > and --delete options. > > - Append a '.' to any "/" source path (i.e. use [EMAIL PROTECTED]:/. ) -- that > bypasses the bug. > > ..wayne.. > -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
