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 Message-ID: <40668DD4ED0FD511B74100E018043B73A51686@brub002a.siemens.be> From: DEVRIENDT ERIK To: "'cygwin AT cygwin DOT com'" Subject: connect() does not work with UNIX domain datagram sockets Date: Tue, 2 Apr 2002 17:50:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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 ? Please reply to me directly because I did not yet subscribe to the mailinglist Erik Devriendt mailto:Erik DOT Devriendt AT siemens DOT be -- 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/