similar to: Rsync 2.6.9pre2 released

https://bugzilla.samba.org/show_bug.cgi?id=13115 Bug ID: 13115 Summary: .yo sources incompatible with current yodl version Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org

Dear rsync people, Today I tried to back up my computer using rsnapshot with the RPM version of rsync-acl 2.6.9pre1 that I built. I tried twice, and both times, rsync encountered some kind of assertion failure. I was trying to reproduce the crash with rsync-acl 2.6.9pre2 and noticed a different bug (described below); when I have a chance, I will go back and investigate the crash further. Rsync

I've just released rsync 2.6.9pre3. This should be the last version before the final 2.6.9 release, and I don't foresee any significant changes between it and the final release. Please test this out and email the rsync mailing list with any questions, comments, bug reports, etc. Thanks! Here are direct links for the tar file and its signature:

I've just released rsync 2.6.9pre3. This should be the last version before the final 2.6.9 release, and I don't foresee any significant changes between it and the final release. Please test this out and email the rsync mailing list with any questions, comments, bug reports, etc. Thanks! Here are direct links for the tar file and its signature:

Wayne, I noticed that you quietly removed the compatibility mode for sending ACLs to rsyncs before 2.6.8 in revision 1.169 of acls.diff. It would be good to document this in the man page. A metapatch to acls.diff that revises the documentation in rsync.yo is attached; I didn't regenerate rsync.1 because I don't have yodl 2 set up. Where did you get the version of yodl 2 that you are

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> zstd compression was announced as "good compression with high throughput" so I gave it a try. With zlib, on high speed links the CPU is usually the bottle neck. With zstd I'm able to fill a 200Mbit link :) zstd detection happens automatically via pkg-config. No zstd header means no error about missing zstd. So that

Here's the latest version of the batch mode cleanup patch. Index: batch.c =================================================================== RCS file: /cvsroot/rsync/batch.c,v retrieving revision 1.12 diff -u -r1.12 batch.c --- batch.c 24 Jan 2002 08:09:46 -0000 1.12 +++ batch.c 6 Feb 2002 19:47:57 -0000 @@ -8,55 +8,38 @@ #include "rsync.h" #include <time.h> -char

Hallo Wayne, > A patch that fixes f_name_cmp() is attached. I'm also considering a more > extensive change that would simplify the logic in f_name_cmp(), but that > will have to wait until after 2.6.5 gets released. Wonderful, the patch works. > > Thanks for the report! Thanks for the very fast analysis of the problem Greetings, Frank

I appear to be hitting a case of premature optimization at my site - with rsync 2.6.4pre2: I backup a number of very large systems using rsync, and have been updating as I try and fix various weird problems. It appears that rsync 2.6.4pre2 fixes some of my other issues (timeouts in particular), but now I'm being bitten by very high loads and slow transfers. My current theory is that the

hi, as it's been awhile since my last attempts w/ v269, i'm building the latest rsync3-svs on osx 10.4.8; looking to see what's evolved re: acls & xattrs support on osx ... @ build, i note complaint abt a missing yodl2man, which originates with YODL. YODL, then requires icmake. as neither is available on osx, it's src build time. on building debian's icmake (already

Dear Wayne, C Sights, and list, I have started working on my rewritten version of the rsync man page. So far, I have redone the top of the man page and the list of options; I improved many of the one-line option descriptions. The yodl and man versions of my man page are available here and here: http://www.kepreon.com/~matt/private/rsync-new-manpage/rsync.yo

I've been having problems trying to sync two small partitions (128MB) that may be near to full. If rsync gets a write error (such as is caused when you fill up a partition) during a sync without the use of "-T", it will stop with this error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream

Hi, I needed to filter content of files (encrypt), before they are sent over the network to backup server. The easiest way to do this was modifying Kyle Jones's "--dest-filter" patch. Somebody was asking there this feature in the past, so I'm sending this patch to list. Implementation details: -filtering disables rsync alogrithm -source filter makes temporary files in /tmp

I've just released rsync 2.6.9pre1, the first pre-release version for the upcoming 2.6.9 release. Please test this out and email the rsync mailing list with any questions, comments, bug reports, etc. Thanks! You can download the tar file and its signature from here: http://rsync.samba.org/ftp/rsync/rsync-2.6.9pre1.tar.gz http://rsync.samba.org/ftp/rsync/rsync-2.6.9pre1.tar.gz.asc

I've just released rsync 2.6.9pre1, the first pre-release version for the upcoming 2.6.9 release. Please test this out and email the rsync mailing list with any questions, comments, bug reports, etc. Thanks! You can download the tar file and its signature from here: http://rsync.samba.org/ftp/rsync/rsync-2.6.9pre1.tar.gz http://rsync.samba.org/ftp/rsync/rsync-2.6.9pre1.tar.gz.asc

I am working on rsync tool. As rsync sends data over SSH in non-daemon mode, it forks the SSH process in pipe.c function. For the communication between the parent rsync and child SSH, it uses the socket pairs. As socket pairs are bidirectional, only one pair can be used for communication between the parent and child. e.g. socketpair(xx,xx,xx,xx) returns -> to_child_pipe[2]={3,4} then these

(I am not on the rsync mailing list, so if you send a response to this message to the list, please be sure to CC me.) I first reported this bug go Red Hat in <URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65350>. If you run rsync with a subshell through ssh.com's ssh and sshd and then kill the client with ctrl-C, the rsync server process running on the remote machine grows

[I sent this the other day, but it never got approved for the list] I've been having problems trying to sync two small partitions (128MB) that are usually near being full. The rsync would fail with this cryptic error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) It ends up

Hello everyone! I didn't find anything in the archives that seemed similar (same error, different offending lines of code). I'm having an issue with rsync on a couple of my servers. A couple of others run just fine but 2 of them give me the same message (see below) when I try to do backups from one server to these linux boxes. All of the linux boxes are the same and have the save

Hi, we ran into a little problem with rsync-2.5.5. Setup: you run rsync-2.5.5 as normal rsync over ssh (ie. not connecting to a rsync server). If you start such a rsync but interrupt the pulling process with Ctrl-C, the process on the other side may start to allocate all memory on the remote machine. As fa as we have analyzed the problem, the remote rsync process wants to issue a error message