Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<409837E7.C09A2D17@hot.pl>
Date:	Wed, 05 May 2004 02:40:07 +0200
From:	Jacek Trzmiel <sc0rp AT hot DOT pl>
MIME-Version:	1.0
To:	"'Cygwin List'" <cygwin AT cygwin DOT com>
Subject:	Re: shutdown( socket, SHUT_WR ) - unexpected behaviour
References:	<NUTMEG3Mpw6yL2m9lHi00000164 AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <409769B5 DOT 6050609 AT earthlink DOT net>
X-IsSubscribed:	yes

Hi,

> > Just kind of wondering if the apache is prematurely dropping the line when
> > it sees the FIN.
> 
> Possible, but I suspect it's a problem on Jacek's machine.

Yep, that's most likely.


> Jacek: Win2K SP2 is pretty ancient. Is it possible to try this on a
> later SP? (SP4 is the latest, and there have been numerous hotfixes
> since it was released.)

I'll try with SP4 later today.


> If upgrading is not feasible, would it be possible for you to capture
> the actual on-the-wire network traffic? That would absolutely pinpoint
> the guilty culprit.

In my other mail: http://cygwin.com/ml/cygwin/2004-05/msg00125.html


Best regards,
Jacek.

--
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/

- Raw text -