X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_40 X-Spam-Check-By: sourceware.org Date: Mon, 23 Feb 2009 09:33:19 -0600 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: Multicast Blocking Receiving Socket in Cygwin In-Reply-To: <22159196.post@talk.nabble.com> Message-ID: References: <22159196 DOT post AT talk DOT nabble DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mon, 23 Feb 2009, victhor_1983 wrote: > I am using a Multicast socket to receive UDP datagrams on Cygwin. I thought > the sockets in Cygwin were blocking by defect (that is, the program waits at > recvfrom() until it read something on the socket). However, my program does > not wait, it keeps running. I didn't use fcntl or any other instruction to > make the socket non-blocking, is there any way to make the socket blocking? You are correct in that they should be blocking by default (and were/are AFAIK). Is this in Cygwin 1.5 or 1.7? Can we see a source fragment? What is errno? -- Brian Ford Staff Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... -- 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/