X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 22 Mar 2010 13:37:56 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: recvfrom + MSG_PEEK = broken? Message-ID: <20100322173756.GB15808@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4BA7085D.3050307@cwilson.fastmail.fm> <20100322110352.GA32321@calimero.vinschen.de> <4BA78525.5080206@cwilson.fastmail.fm> <20100322160100.GA7186@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100322160100.GA7186@calimero.vinschen.de> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mon, Mar 22, 2010 at 05:01:00PM +0100, Corinna Vinschen wrote: >On Mar 22 10:56, Charles Wilson wrote: >> On 3/22/2010 7:03 AM, Corinna Vinschen wrote: >> > On Mar 22 02:04, Charles Wilson wrote: >> >> I've been tracking down a problem in xinetd. It appears to be an issue >> >> with using MSG_PEEK in recvfrom() on UDP sockets. >> > >> > Yes, that's a bug in Cygwin. The socket event handling got messed up >> > when MSG_PEEK was used. I fixed that in CVS so it will be in 1.7.2. >> >> Confirmed: fixes both my testcase, and the error in xinetd. Thanks for >> the quick turnaround! I was about ready to pull my hair out on this > >Sure. I'm glad I had a simple testcase for a socket problem. If only >somebody would come up with an equally simple testcase for the rsync >problem... I thought the rsync problem was due to the fact that select for write on pipes is unreliable. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple