X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4BA76670.6000402@cs.umass.edu> Date: Mon, 22 Mar 2010 08:45:36 -0400 From: Eliot Moss User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: recvfrom + MSG_PEEK = broken? References: <4BA7085D.3050307@cwilson.fastmail.fm> <20100322110352.GA32321@calimero.vinschen.de> In-Reply-To: <20100322110352.GA32321@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 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. > The last time I had problems with MSG_PEEK was back in 2006. Curious > how seldomly it's used, apparently. > > Thanks for the simple testcase! It was very helpful to track down > the problem easily. I wonder if rsync uses MSG_PEEK? If it does, could this explain the rsync spinning problem that gets fixed (for me anyway) by not using socketpair? Regards -- Eliot Moss -- 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