Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 27240 invoked by uid 500); 3 Feb 2003 22:23:36 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 27192 invoked from network); 3 Feb 2003 22:23:35 -0000 Message-ID: <3E3EEBE4.4060402@wstoddard.com> Date: Mon, 03 Feb 2003 17:23:32 -0500 From: Bill Stoddard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@apr.apache.org Subject: Re: apr_socket_accept() interrupted on Win32 corrupts master socket? References: <5.2.0.9.2.20030203145316.02328858@pop3.rowe-clan.net> In-Reply-To: <5.2.0.9.2.20030203145316.02328858@pop3.rowe-clan.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N William A. Rowe, Jr. wrote: >Vaclav, yes- this is a 'windoze thingy' :-) > > Hummm perhaps... However, if the listener is really whacked after the timeout, then I would think the problem is in either apr_socket_accept for windows or more likely a bug in the application. Bill