Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Mon, 3 Feb 2003 17:16:33 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: socketpair(AF_UNIX, SOCK_STREAM, 0, fd) failing: errno 112, Address already in use
Message-ID: <20030203161633.GE21956@cygbert.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <00de01c2c701$ac90f130$78d96f83@pomello> <20030203160004.GC21956@cygbert.vinschen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030203160004.GC21956@cygbert.vinschen.de>
User-Agent: Mutt/1.4i

On Mon, Feb 03, 2003 at 05:00:04PM +0100, Corinna Vinschen wrote:
> On Tue, Jan 28, 2003 at 07:15:52PM -0000, Max Bowsher wrote:
> > I'm seeing rsync failiures due to socketpair(AF_UNIX, SOCK_STREAM, 0, fd)
> > failing with errno 112, Address already in use.
> > 
> > As far as I know, this shouldn't be able to occur. This seems to me like a
> > Cygwin bug? If it is, then this is a bug report.
> 
> Would you mind to create a test case?

Or, on second thought, first try running rsync under strace.  socketpair()
gives some important hints in which part of the implementation the error
occurs.  The debug output of the failing socketpair() call would be
interesting to see...

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

