rsync - Nov 2009 - dup error of rsync 3.0.6-1 under cygwin 1.7.0-62 and 63

I have used earlier rsync on cygwin successfully for a
long. I have now moved to cygwin 1.7.0, which required
moving to rsync 3.0.6-1 at the same time. (The -1 is
for minor cygwin-specific patches.)

When I do almost any command with rsync, such as the one
below, it breaks at a dup2 after a fork in pipe.c (routine
piped_child). Windows gives error code 6, which is translated
by cygwin to errno 9 = EBADF, and rsync then terminates.

rsync -avzuP foo roc:talks/

Even

rsync -r .

fails the same way, though it does not need a network
connection.

Steven Monai suggests that the problem may be a mismatch
in protocol (30 versus 29), though I think the last command
scuttles that possibility. I think it has something to do
with cygwin, since cygwin 1.5 seemed ok, but it could be
a combination of changes un rsync and cygwin ...

Best wishes -- Eliot Moss
=============================================================================J.
Eliot B. Moss, Professor               http://www.cs.umass.edu/~moss    www
Director, Arch. and Lang. Impl. Lab.      +1-413-545-4206                voice
Department of Computer Science            +1-413-695-4226                 cell
140 Governor's Drive, Room 372            +1-413-545-1249                 
fax
University of Massachusetts at Amherst    moss at cs.umass.edu             
email
Amherst, MA  01003-9264  USA              +1-413-545-2746 Laurie Downey 
sec'y
==============================================================================

Eliot Moss wrote:
> I have used earlier rsync on cygwin successfully for a
> long. I have now moved to cygwin 1.7.0, which required
> moving to rsync 3.0.6-1 at the same time. (The -1 is
> for minor cygwin-specific patches.)
> 
> When I do almost any command with rsync, such as the one
> below, it breaks at a dup2 after a fork in pipe.c (routine
> piped_child). Windows gives error code 6, which is translated
> by cygwin to errno 9 = EBADF, and rsync then terminates.
> 
> rsync -avzuP foo roc:talks/
> 
> Even
> 
> rsync -r .
> 
> fails the same way, though it does not need a network
> connection.
> 
> Steven Monai suggests that the problem may be a mismatch
> in protocol (30 versus 29), though I think the last command
> scuttles that possibility. I think it has something to do
> with cygwin, since cygwin 1.5 seemed ok, but it could be
> a combination of changes un rsync and cygwin ...
Thought I'd give the rsync HEAD a try on this, since it
does include changes in the I/O part of the world. It fails
in exactly the same way ... (but in io.c, of course).

Cheers -- Eliot