From owner-freebsd-stable Fri Sep 29 10:38: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4203637B424 for ; Fri, 29 Sep 2000 10:38:02 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8THbvW11701; Fri, 29 Sep 2000 10:37:57 -0700 (PDT) Date: Fri, 29 Sep 2000 10:37:57 -0700 From: Alfred Perlstein To: Daniel Eischen Cc: Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: Re: pthreads bug? Message-ID: <20000929103756.I27736@fw.wintelcom.net> References: <20000929013521.C27736@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from eischen@vigrid.com on Fri, Sep 29, 2000 at 07:28:54AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Daniel Eischen [000929 04:29] wrote: > > I don't think it should be fixed unless we decide to remove the > automatic locking of file descriptors. But if you do come up > with a clean solution, please run it by me. I have some massive > changes to the threads library that are currently under review. Well the hackish idea that I had was to set the thread runnable but somehow set a flag so that it knows it's the "accept() being broken by close() wakeup." The accept()ing thread can then unlock the file and return EBADF or whatever it's supposed to. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message