X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4BA7AB94.8060702@cs.umass.edu>
Date: Mon, 22 Mar 2010 13:40:36 -0400
From: Eliot Moss <moss AT cs DOT umass DOT edu>
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 AT cygwin DOT com
Subject: Re: recvfrom + MSG_PEEK = broken?
References: <4BA7085D DOT 3050307 AT cwilson DOT fastmail DOT fm>  <20100322110352 DOT GA32321 AT calimero DOT vinschen DOT de>  <4BA78525 DOT 5080206 AT cwilson DOT fastmail DOT fm>  <20100322160100 DOT GA7186 AT calimero DOT vinschen DOT de> <20100322173756 DOT GB15808 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20100322173756.GB15808@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 3/22/2010 1:37 PM, Christopher Faylor wrote:
> 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.

Could be -- 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