X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <20081028132256.33168.qmail@web4103.mail.ogk.yahoo.co.jp> Date: Tue, 28 Oct 2008 22:22:55 +0900 (JST) From: neomjp Subject: Re: cygport/rsync problem To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I wrote this mail as a reply to http://sourceware.org/ml/cygwin-apps/2008-10/msg00075.html but let me post it here because I am not a package maintainer and am not a subscriber to cygwin-apps. On 2008/10/26 21:42, Steffen Sledz wrote: > 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.4-1/src/rsync-3.0.4/pipe.c(147) [receiver=3.0.4] > rsync: read error: Connection reset by peer (104) > rsync error: error in IPC code (code 14) at /home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/io.c(791) [sender=3.0.4] This is probably the same error as the one that I had when using rsync in cygwin-1.7. It is probably caused by some firewall or anti-virus software blocking the operation of rsync. In my case, the culprit was NOD32. When I ran rsync in gdb, $ mkdir somedir $ touch somedir/somefile $ gdb --args /usr/bin/rsync -a somedir/ anotherdir GNU gdb 6.8.0.20080328-cvs (cygwin-special) ..... (no debugging symbols found) (gdb) run Starting program: /usr/bin/rsync -a somedir/ anotherdir ..... (no debugging symbols found) warning: NOD32 protected [MSAFD Tcpip [TCP/IP]] warning: NOD32 protected [MSAFD Tcpip [UDP/IP]] warning: NOD32 protected [MSAFD Tcpip [RAW/IP]] warning: NOD32 protected [RSVP UDP Service Provider] warning: NOD32 protected [RSVP TCP Service Provider] (no debugging symbols found) (no debugging symbols found) ---Type to continue, or q to quit--- (no debugging symbols found) [New thread 1508.0x720] [New thread 1508.0xeb0] [New thread 1508.0x54c] 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.4-1/src/rsync-3.0.4/pipe.c(147) [receiver=3.0.4] I have had no problems with rsync in cygwin-1.5 and NOD32. There must be some changes in the implementation of socket/IPC/pipe between cygwin-1.5 and -1.7, which NOD32 does not like. I did not track it down further because this is a problem of NOD32 and because the workaround was simple: add rsync to the exception list of NOD32. -------------------------------------- Enjoy MLB with MAJOR.JP! Ichiro, Matsuzaka, Matsui, and more! http://pr.mail.yahoo.co.jp/mlb/ -- 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/