Date: Wed, 25 Nov 1998 06:23:12 -0500 (EST) From: HighWind Software Information <info@highwind.com> To: info@highwind.com Cc: current@FreeBSD.ORG Subject: Re: close() can hang! Message-ID: <199811251123.GAA29928@highwind.com> In-Reply-To: <199811250725.CAA27686@highwind.com> (message from HighWind Software Information on Wed, 25 Nov 1998 02:25:34 -0500 (EST))
next in thread | previous in thread | raw e-mail | index | archive | help
Responding to myself... --- A libc_r linked program starts up, binds a TCP port, dup2()'s the socket to STDIN and execv()'s another libc_r linked program. The new libc_r linked program starts a thread that calls "accept()" on STDIN. Once that happens. If the new program calls "close()" STDIN, it hangs! All fd's are blocking fd's at the application level. --- It actually simply has to do with calling "close()" on an fd that another thread is "accept()"'ing on. It appears that FreeBSD doesn't like it when you to do that. -Rob 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?199811251123.GAA29928>