Cygwin1.dll 1.7.0-5x: RSYNC failures in close() system call on pipe file descriptors
Angelo Graziosi
angelo.graziosi@alice.it
Sun Aug 16 00:22:00 GMT 2009
Corinna Vinschen wrote:
> On Aug 14 00:07, Angelo Graziosi wrote:
>> Christopher Faylor wrote:
>>
>>> "Socket operation on non-socket" sounds like the problem that
>>
>> I am just a little curious, is the discussion in this thread related to
>> what I flagged here:
>>
>> http://cygwin.com/ml/cygwin/2007-04/msg00143.html
>>
>> and here:
>>
>> http://cygwin.com/ml/cygwin/2007-05/msg00677.html ?
>
> No, that's probably not related.
Hmm... finally, I decided to give a new try to 1.7 :-)
Now, the output of rsync is a little different from that I have reported
in [1]:
$ rsync testo /tmp/
rsync: Failed to dup/close: Socket operation on non-socket (108)
rsync error: error in IPC code (code 14) at
/home/lapo/packaging/rsync-3.0.5-1/s
rc/rsync-3.0.5/pipe.c(147) [receiver=3.0.5]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
/home/lapo/packagi
ng/rsync-3.0.5-1/src/rsync-3.0.5/rsync.c(544) [sender=3.0.5]
but... for what I can understand from this thread... it looks to me
related! ;-)
Cheers,
Angelo.
---
[1] http://cygwin.com/ml/cygwin/2007-05/msg00677.html
--
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
More information about the Cygwin
mailing list