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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 04 Mar 2002 10:56:50 -0500 From: Jason Tishler Subject: recv(..., MSG_PEEK) (was Re: fetchmail 5.9.8 and maildrop 1.3.7) In-reply-to: <20020303155818.A3120@LOKI> To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20020304155650.GA1424@hp.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: <20020302004512 DOT A1936 AT LOKI> <20020302160332 DOT GA1976 AT hp DOT com> <20020302221220 DOT A4040 AT LOKI> <20020303024718 DOT GB2116 AT hp DOT com> <20020303155818 DOT A3120 AT LOKI> Corinna, On Sun, Mar 03, 2002 at 03:58:18PM +0000, Rui Carmo wrote: > On Sat, Mar 02, 2002 at 09:47:19PM -0500, Jason Tishler wrote: > > > I was under the impression that recv() bugs had been twiddled in > > > 1.3.10... Or did the changes in recv() not address MSG_PEEK? > > > > Hmm, I will look into this. It would be great if my patch just became > > obsolete. > > The release notes (post by Cristopher: > http://sources.redhat.com/ml/cygwin/2002-02/msg01350.html) mention recv() > explicitly: > > > - Implement socket read/write using recv/send. (corinna) > > Bit vague, though, so I don't know if Corinna tackled the MSG_PEEK > issue. Could you comment as to whether or not the above changes would have any positive affects on the following? http://sources.redhat.com/ml/cygwin/2001-08/msg00628.html I could just try to determine this empirically, but since this is very disruptive to my mail delivery, I was hoping for a "warm fuzzy" first. Thanks, Jason -- 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/