From owner-freebsd-current Tue Sep 8 15:22:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24980 for freebsd-current-outgoing; Tue, 8 Sep 1998 15:22:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (ts02-057.dublin.indigo.ie [194.125.134.187]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24947 for ; Tue, 8 Sep 1998 15:22:14 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id XAA01106; Tue, 8 Sep 1998 23:15:54 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199809082215.XAA01106@indigo.ie> Date: Tue, 8 Sep 1998 23:15:53 +0000 In-Reply-To: <199809081812.LAA02029@usr07.primenet.com>; Terry Lambert Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: info@highwind.com Subject: Re: Thread Problems Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 8, 6:12pm, Terry Lambert wrote: } Subject: Re: Thread Problems > > > > That is it. The application SITS idle right here. Doing NOTHING. It > > will respond to additional connections. So, it appears that the > > "accept()" thread is still responsive. However, all other threads are > > not responsive. > > You are aware of the fact the socket options are not inherited > across a dup, dup2, fcntl( ..., F_DUPFD, ...), connect, accept, > bind, etc., right? > > Frankly, this looks like the fd is not async. The only potentially > blocking call should be select(). But it's the thread library's responsability not to call accept until it is sure that the call will not block.... Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message