similar to: 2.6.4 Potential protocol-corrupting bug

Hi all, I'm running rsync version 2.6.3 protocol version 28 on Solaris 8 and am having a problem. We have some scripts that wrap around rsync and generate a list of files to transfer from the sending system (regardless of whether that directory exists on the receiver). I was expecting rsync to fail when transferring files with a path that doesn't exist on the receiver (in fact

Sorry, aber 2.6.4 ist ZIEMLICH GEIL. Da m?ssen wir mal die neuen schalterchen ausprobieren. (delete-after zum Beispiel) Ich lass Dich raus aus so was. Gruss Markus -----Urspr?ngliche Nachricht----- Von: rsync-announce-bounces+ulrichd=voelcker.com@lists.samba.org [mailto:rsync-announce-bounces+ulrichd=voelcker.com@lists.samba.org] Im Auftrag von rsync-announce@lists.samba.org Gesendet:

I am wondering if there are known incompatibilities between 2.6.3 and 2.6.4? I have a debian box with 2.6.4 and a FC3 box with 2.6.3. Most of the time rsync works fine between the two but I am running this command on FC3 box: rsync -azvv --stats --delete --files-from=/root/.rsb2.tmp / nathan@debian:/home/backup/bkp.01 And I am getting this error message: building file list ... [sender] expand

I've released rsync 2.6.4pre4. I believe that this version will be what gets released as 2.6.4, hopefully on Wednesday. Please try this out and let me know if anything is amiss. All the changes since 2.6.3 are mentioned here: http://rsync.samba.org/ftp/rsync/preview/NEWS You'll also find a preview of the man pages in the same dir (as usual):

I've released rsync 2.6.4pre4. I believe that this version will be what gets released as 2.6.4, hopefully on Wednesday. Please try this out and let me know if anything is amiss. All the changes since 2.6.3 are mentioned here: http://rsync.samba.org/ftp/rsync/preview/NEWS You'll also find a preview of the man pages in the same dir (as usual):

I installed the newly released version of cwRsync today on a few Windows machines and have noticed a new problem that I have not seen mentioned anywhere. When syncing to an NT machine used for backups, my rsync client exited at the end of the transfer with the following message to standard error: multiplexing overflow 1:296 [sender] rsync error: error in rsync protocol data stream (code 12)

I believe I have encountered a nasty bug with rsync 2.6.6 "--delete-excluded" option. When this is enabled, rsync''s operation appears to break entirely. I have a script that I''ve been using for a few years. The script hasn''t changed in the last year or so. Recently I upgraded from SuSE 9.3 to SUSE 10.0 which means that I went from rsync 2.6.3 (+ patches,

I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS,

What the maximum filesize rsync can transfer? I'm trying to rsync one of my servers to another but the rsync is croaking on a file that's barely 1GB. Tips, hints, suggestions? rsync server is AIX 4.3.3 ML11 - rsync 2.6.3 rsync client is AIX 5.3 ML1 - rsync 2.6.4 Thanks -Jeff -- Jeff Schoby Unix/Network Admin City of Columbia, Missouri 573.874.6320

https://bugzilla.samba.org/show_bug.cgi?id=2583 Summary: rsync fails with "authentication failure" Product: rsync Version: 2.6.4 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: hpa@zytor.com

On 10/08/2012 21:58, nut-upsuser-request at lists.alioth.debian.org wrote: >>> Arnaud Quette<aquette.dev<at> gmail.com> writes: >>>> 2012/6/3 Chris Rees<crees<at> freebsd.org>: >>>>> Hi all, >>>> Hi Chris, >>>> >>>>> After some research I've found that this device should run with the

I have released rsync 2.6.4. This version has quite a few enhancements over 2.6.3, some optimizations in the delete handling, and the usual collection of bug fixes. I'd like to say "thanks" to everyone who downloaded and tested one of the pre-release versions -- the feedback was very helpful! A summary of the changes since 2.6.3 is available here:

I have released rsync 2.6.4. This version has quite a few enhancements over 2.6.3, some optimizations in the delete handling, and the usual collection of bug fixes. I'd like to say "thanks" to everyone who downloaded and tested one of the pre-release versions -- the feedback was very helpful! A summary of the changes since 2.6.3 is available here:

https://bugzilla.samba.org/show_bug.cgi?id=2628 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|hangs indefinitely (while |hangs indefinitely at start |listing files) |of phase 1 ------- Additional Comments From wayned@samba.org

Running rsync against an old server I get: rsync rsync://host/dir rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync: error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.0] This seem to be a problem described in the second paragraph of the release notes. The notes say to use --no-d, but using it seem not to help, and in fact the remote

Hi, I got this error after a transaction was interrupted by me and a new (slightly updated) transaction was started. ... fedora/1/en/i386/base/pkglist.dag.bz2 1246954 100% 67.79kB/s 0:00:17 (27, 1.7% of 201557) Invalid file index 1777522462 (count=201557) rsync error: protocol incompatibility (code 2) at sender.c(152) On both ends exactly the same rsync was used. It's a

What does rsync do with permissions? Using rsync -auvP ./* targetMachine:/targetDir I sometimes get an error/warning such as: chown GENERO/uk/reinsure/prod/rel/dbmodify.4gl : Operation not permitted The source file has owner/group stevet:dev and the target stevet:users The files are being rsync'd as user 'fyl' - fyl belongs to both dev and users group. The 'oddity' is

https://bugzilla.samba.org/show_bug.cgi?id=2645 Summary: --one-file-system semantics changed with 2.6.4 (bug?) Product: rsync Version: 2.6.4 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

Hi everyone, I'm using Samba3.0.2a, Openldap-2.1.30 for authentication and about 150 Windows XP computers as clients. I was able to join all my XP clients to my domain. But for sometime now, my ldap database keeps on corrupting for an unknown reason when a lot of my users log in to my PDC... Can anyone help me find the reason of this corruption or has the same problem that I have? Please

I'm very new to Samba, and I'm supporting my team's migration to a new server. We are running v3.0.23b, ML3 and AIX v5.3, and we're pulling data from NT servers. V2.2.2 (what we are using on the old server) would not compile on the new box, so we have to upgrade. Files >2.8gb are corrupting during the transfer. That 2.8gb file is the largest we've gotten to go through