Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 2 Apr 2002 18:12:01 +0200 From: Corinna Vinschen To: DEVRIENDT ERIK Cc: cygwin Subject: Re: connect() does not work with UNIX domain datagram sockets Message-ID: <20020402181201.I1475@cygbert.vinschen.de> Mail-Followup-To: DEVRIENDT ERIK , cygwin References: <40668DD4ED0FD511B74100E018043B73A51686 AT brub002a DOT siemens DOT be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40668DD4ED0FD511B74100E018043B73A51686@brub002a.siemens.be> User-Agent: Mutt/1.3.22.1i On Tue, Apr 02, 2002 at 05:50:21PM +0200, DEVRIENDT ERIK wrote: > Hi, > > I am porting a client-server set of programs that run > fine under linux. > The programs communicate using UNIX domain datagram sockets. > the server does the classic socket(), unlink(), bind() and then a loop > with read(). There is no accept() because we use datagram > sockets. > > The problem is in the client, which does socket(), connect() > and then a loop with write() calls. > The connect() hangs for 10 seconds and then fails with errno=111 > (Connection refused). > When using sendto() I manage to send data, but that doesn't fit well > in the current implementation of the client (we use the same > codebase for several platforms). > According to the man pages of select() on linux and HP-UX it is allowed > to use connect() with datagram sockets; it sets the default destination > address for the communication over that socket. > > Is this a cygwin bug, or am I doing something wrong ? Could you please test if it works when omitting the unlink() on the server side? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT 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/