rsync fork/exec problem with odd twist for native windows programs

Sat Feb 18 04:28:00 GMT 2006

	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 10 minutes, I'm inclined to point the finger at
	rsync. However, I use the same version of rsync on another
	system where it runs like a champ. That doesn't leave any
	suspects.
	I'm still puzzled as to why even true.exe hung. I did not
	want to make my problem report even longer, but I had another
	test program which was literally "int main() { exit(0) }",
	just in case true.exe was not as minimal as expected. That
	test program also hung when spawned by rsync.
		Scott
On 2006年2月17日 18:11:40 -0500, "Brett Serkez" wrote:
> Scott,
>> <snip>
> > 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 seemingly hangs in the same/similar place, in my case I substituted
> the use of a local pipe for a local socket to resolve.
>> > However, a netstat on the remote host did not show any connection.
> > Btw, when I call ssh directly it works just fine.
>> Yes, same here.
>> Brett
> ----------------------------------------------------------------
> Brett C. Serkez, Techie
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/