From owner-freebsd-current Wed Nov 25 03:23:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23708 for freebsd-current-outgoing; Wed, 25 Nov 1998 03:23:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23703 for ; Wed, 25 Nov 1998 03:23:18 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id GAA29928; Wed, 25 Nov 1998 06:23:12 -0500 (EST) Date: Wed, 25 Nov 1998 06:23:12 -0500 (EST) Message-Id: <199811251123.GAA29928@highwind.com> From: HighWind Software Information To: info@highwind.com CC: current@FreeBSD.ORG In-reply-to: <199811250725.CAA27686@highwind.com> (message from HighWind Software Information on Wed, 25 Nov 1998 02:25:34 -0500 (EST)) Subject: Re: close() can hang! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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