On Apr 27 20:15, Steven Hartland wrote: > ----- Original Message ----- > From: "Christopher Faylor" <[EMAIL PROTECTED]> > > > "Search for cygwin1.dll using the Windows Start->Find/Search facility > > and delete all but the most recent version. The most recent version > > *should* reside in x:\cygwin\bin, where 'x' is the drive on which you have > > installed the cygwin distribution. Rebooting is also suggested if you > > are unable to find another cygwin DLL." > > Stupid me, perl.exe still running in the background using the old .dll. > Things now run by unfortunately rsync is still hangs virtually > instantly :( > > [log] > rsync -av --progress cygwin1:/testdir/ testdir/ > receiving file list ... > 1705 files to consider > created directory testdir > ./ > bf2_w32ded.exe > ***HUNG HERE*** > ^CKilled by signal 2.0.00kB/s 0:00:00 > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(242) > [receiver] > rsync error: unexplained error (code 255) at rsync.c(242) [generator] > [/log]
Damn (sorry). It works fine for me with the latest snapshot. I tried Peter's example with 1000 files and rsync over ssh works like a charm for me. Sigh. This is really a tricky problem. What I could do to circumvent this at least for connections over ssh is to upload an OpenSSH test version which uses socketpairs instead of pipes for the local connection to the applications. This avoids using pipes which are the culprit here, apparently. I would mark it as experimental version, but actually the only difference would be that it would be a few per cent slower than the version using pipes. And that it probably doesn't hang. Is there interest in such a version? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
