Using a self-built rsync 3.0.7 without socket pairs, I've
encountered a problem using snapshots later than 2010-03-28.
{{{
% rsync --version
rsync version 3.0.7 protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
no socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes
rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. See the GNU
General Public Licence for details.
% date > t
% rm -f t2
% rsync -avi t t2
sending incremental file list
>f+++++++++ t
rsync: connection unexpectedly closed (28 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at
/usr/src/rsync/rsync-3.0.7-1dcr1/src/rsync-3.0.7/io.c(601) [sender=3.0.7]
}}}
It seems the copy works, but I do get this error message. Other
rsync operations of real (larger) files appear to hang.
I didn't notice any problems with the stock rsync, but I didn't do
much testing.
Reverting back to the 2010-03-28 snapshot solves the problem.
--
David Rothenberger ---- daver...@acm.org
Deja vu:
French., already seen; unoriginal; trite.
Psychol., The illusion of having previously experienced
something actually being encountered for the first time.
Psychol., The illusion of having previously experienced
something actually being encountered for the first time.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
