Scott,
> Thanks for the suggestion. Switching from socketpair() to
> pipe() does let ssh get going, but rsync later runs into
> problems. A few minutes into the transfer it just hangs.
I've actually been able to run fine once past the initial hang, but I've
seen reports of rand
Brett,
Thanks for the suggestion. Switching from socketpair() to
pipe() does let ssh get going, but rsync later runs into
problems. A few minutes into the transfer it just hangs.
Since I exercised ssh by transferring 16MB files back and
forth for 1
Scott,
> I started this investigation when rsync spawning ssh hung. By using
> the -vv verbose option I could tell that rsync was starting ssh.
It is difficult to tell if this is the same or similar to the rsync hang
I experienced:
http://sourceware.org/ml/cygwin/2005-12/msg01096.html
It seemi
I've found an rsync problem that might be another data point for the
fork() (or exec()?) problems mentioned on the cygwin mailing list last
fall. On one of my systems rsync hangs after it forks a cygwin program.
Surprisingly, when it forks some native windows program, it completes.
I started this
4 matches
Mail list logo
