Date: Tue, 8 Sep 1998 18:12:33 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: info@highwind.com (HighWind Software Information) Cc: freebsd-current@FreeBSD.ORG Subject: Re: Thread Problems Message-ID: <199809081812.LAA02029@usr07.primenet.com> In-Reply-To: <199809070646.CAA01061@highwind.com> from "HighWind Software Information" at Sep 7, 98 02:46:30 am
next in thread | previous in thread | raw e-mail | index | archive | help
> Here at HighWind we are trying (really hard) to get our products to > work under FreeBSD. We tried v2.2.X and failed. Now, we are trying 3.0 > and also failing. > > Currently the situation is as follows, on startup, our application > starts a number of threads (via pthread_create). One calls "accept()", > others go off and do lots of "mmap()"'s to files and do other stuff to > various files on the local disk. > > After the first accept() comes in, the application appears to become > unresponsive. That is, the other threads make no progress. Check out > the ktrace: > 21620 typhoond CALL accept(0x6,0x10afd8,0x10afd4) > > 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(). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. 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?199809081812.LAA02029>