From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 00:42:06 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A09A616A4CE for ; Fri, 18 Feb 2005 00:42:06 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DB0243D39 for ; Fri, 18 Feb 2005 00:42:06 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id 0319246B29; Thu, 17 Feb 2005 19:42:06 -0500 (EST) Date: Fri, 18 Feb 2005 00:40:39 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bill Fenner In-Reply-To: <200502180037.j1I0bu9F001044@bright.research.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: net@freebsd.org Subject: Re: solisten() question: why do we check for completed connections? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 00:42:06 -0000 On Thu, 17 Feb 2005, Bill Fenner wrote: > which looks like it's initializing q0 and q to be circular queues, which > has to only happen once, and also setting SO_ACCEPTCONN; since nothing > ever turns off SO_ACCEPTCONN, this is not something that has to happen > only once. When the stuff that had to happen only once got removed, the > conditional remained. > > So, I'd say that setting SO_ACCEPTCONN is required, but the conditional > is not. I don't know if that helps your race or not. This sounds like just the explanation I was looking for. Thanks, Robert N M Watson