Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <001701c076ba$796c9e10$8553b4ca@private> From: "David McNab" To: Cc: "Andrew M. Bishop" Subject: CloseSocket() problem Date: Thu, 4 Jan 2001 17:54:39 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Hi Corinna, On searching through Cygwin mail archives, I note that you've had problems with closing down sockets in child processes. I have experienced the same thing. I'm presently working on testing the Win32 Cygwin port of another developer's proxy server program (called WWWOFFLE, see http://www.gedanken.demon.co.uk/wwwoffle/). On re-compiling the program with the cygwin v1.1.7.1 dll, I noticed Microsoft Internet Explorer complaining that the server connections had been reset. I have added code to the applicable child process which fcntl()'s the client socket to blocking mode, then writes a byte of data. This is an attempt to ensure that all data send()'ed to Internet Explorer has actually been sent prior to the CloseSocket(). This hack seems to improve things dramatically, but the problem still shows when sending larger volumes of data back to Internet Explorer. Can you please advise on the status of this CloseSocket() problem, and 1) Any suggestions for a workaround, and/or 2) Whether there are any interim fixes available Kindest thanks in advance David McNab david AT rebirthing DOT co DOT nz -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple