Date: Tue, 8 Sep 1998 23:15:53 +0000 From: Niall Smart <rotel@indigo.ie> To: info@highwind.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Thread Problems Message-ID: <199809082215.XAA01106@indigo.ie> In-Reply-To: <199809081812.LAA02029@usr07.primenet.com>; Terry Lambert <tlambert@primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809082215.XAA01106>