Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Message-ID: <409769B5.6050609@earthlink.net> Date: Tue, 04 May 2004 12:00:21 +0200 From: Keith Moore User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: "'Cygwin List'" Subject: Re: shutdown( socket, SHUT_WR ) - unexpected behaviour References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: bd47eb33e10cdf15d780f4a490ca69564776905774d2ac4b9eb07f69599b97e06f2a7a2d78aa3741350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Dave Korn wrote: > 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. 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.) 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. KM -- 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/