similar to: NOTE for users of the CVS version of rsync

On 3/2/07, Wayne Davison <wayned@samba.org> wrote: > Make the auto-generated protect filters use the perishable flag so > that they don't stop a vanished directory from being removed. 1. I don't think the --backup rule should be perishable. If I delete an entire directory from the source, I would expect the receiver to back up the files inside and not discard the backups just

Dear rsync people (particularly Wayne), I am finding that the CVS version of rsync hangs during most, but not all, local copies. The problem goes away if I pass --protocol=29, so I'm guessing it is related to the incremental file-list sending. The hanging seems to be timing-dependent. Increasing the verbosity level seems to increase the chance of a hang. If I run rsync repeatedly with the

> Date: Sun, 24 Jan 2016 15:43:20 -0800 > From: Wayne Davison <wayne at thedavisons.net> A couple questions below; please bear with me. > No, if you do a ext4 -> ext4 copy, rsync has set the matching ns info for > transferred files since 3.1.0. There was a case prior to rsync 3.1.2 where > a brand-new file transferred in the same second it was created

https://bugzilla.samba.org/show_bug.cgi?id=10532 Summary: Rsync fails with older version. Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: r.e.wolff at bitwizard.nl

On 10/8/06, the CVS server wrote on behalf of Wayne Davison <wayned@samba.org>: > Log Message: > Clarify the short description of --chmod. (i.e., from "change destination permissions" to "change the permissions of transferred files") I'm not sure this clarification is an improvement. --chmod affects all files in the file list, but only some of the regular

https://bugzilla.samba.org/show_bug.cgi?id=8565 Summary: rsync hangs when using --only-write-batch and --hard-links Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

On 6/30/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > checksum-xattr.diff > Log Message: > A simple patch that lets rsync use cached checksum values stored in > each file's extended attributes. A perl script is provided to create > and update the values. Wayne, You should be aware of two drawbacks of caching checksums in xattrs: First,

I've released version 2.6.0 of rsync. Two important things to note in the new release: 1. The default remote shell is now "ssh" unless you tell the configure you want to use something else. 2. Some bug fixes in the include/exclude code, while making things work properly, have resulted in some user-visible changes for certain wildcard strings. Read the

I've been trying to set up a script (inspired by Mike Rubel's scripts) to perform rotating snapshots of the users folders on a Windows server. The machine storing the snapshots is Linux. I have the Windows machine configured as an rsync server, with rsync 2.5.6 and cygwin 1.5.7-1, and the Linux machine has rsync 2.6.0 The objective is to have regular snapshot backups that users can

Hello all, long first post, sorry. I've been using rsync in a backup script for several years now. The script has been stable, and the backup system as a whole pretty much error free for at least 2 years, the only hiccups being minor tweaks to accommodate changes to base utilities used (lvm, namely). In broad strokes, here is what happens for the home directory on my notebook(s). 0.

Hopefully the email to the announce list will show up soon. Until then, you can get a jump on the rest by checking out the rsync home page to read the announcement: http://rsync.samba.org/ It includes a security note about a fix that affects read/write daemons that are not using chroot. If that includes you, you should look into upgrading (or maybe enabling chroot on an older rsync).

On Mon, 10 Nov 2003, Wayne Davison <wayned@samba.org>?wrote: > >?... This fix is also in CVS (along with several others). As another poster pointed out recently, it's been a long time since 2.5.6 was released (Jan 28 2003). Many recent replies to questions posted to this list are variants of "It's already fixed in CVS". Are there any particular reasons for holding

I think it's about time to start adding some new features to rsync 3 instead of just making bug fixes, so I'm planning to starting work on version 3.1.0. This will start the use of a new version numbering idiom where feature releases increment the sub-version number, while patch releases continue to increment the sub-sub-version number. I'm not using an odd/even scheme for

Hi, I've wanted to start working with this CVS version cuz the new "incremental-recursion algorithm" is just what I need. But ran into a problem... When I start the rsync, either with the rsync protocol or rsh, i found that it'll start doing the rsync and just halt after a few hundred MBs or even up to a couple GBs. I was never able to finish an rsync. Anyone else had this

https://bugzilla.samba.org/show_bug.cgi?id=11571 Bug ID: 11571 Summary: rsync-3.1.1 --link-dest arbitrary limit Product: rsync Version: 3.1.1 Hardware: x86 OS: Linux Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Rsync release 2.5.6 is now available at http://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz ftp://ftp.samba.org/pub/rsync/rsync-2.5.6.tar.gz rsync://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz There is a '.sig' file at corresponding URLs with a gpg signature; the public key is available on the pgp keyservers. NEWS for rsync version 2.5.6, aka the dwd-between-jobs release Changes

There is a new patch named "delete-during.diff" in the CVS "patches" dir. This patch adds the ability for rsync to incrementally delete files in each directory during the normal course of the transfer rather than doing a separate delete scan either before or after the transfer. The patch renames the current --delete option into --delete-before and makes --delete behave in the

Wayne, others, Using the same version on server and client, I still got this error. This was still based on last night's CVS (HEAD-20050314-1745GMT) and I am certain both side's versions are identical. :) ... source/sudosh-1.4.7-1.rf.src.rpm 98373 100% 536.69kB/s 0:00:00 (798, 99.9% of 244497) Invalid packet at end of run [sender] rsync error: protocol incompatibility

https://bugzilla.samba.org/show_bug.cgi?id=10226 Summary: fatal_unsafe_io_error and the version it reports Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: Martin.vGagern at

https://bugzilla.samba.org/show_bug.cgi?id=5301 Summary: rsync 3.0.0 copyright dates not updated to 2008 Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: michael@usg.edu