Date: Fri, 29 Sep 2000 10:37:57 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Daniel Eischen <eischen@vigrid.com> Cc: Roman Shterenzon <roman@harmonic.co.il>, freebsd-stable@FreeBSD.ORG Subject: Re: pthreads bug? Message-ID: <20000929103756.I27736@fw.wintelcom.net> In-Reply-To: <Pine.SUN.3.91.1000929072626.7930A-100000@pcnet1.pcnet.com>; from eischen@vigrid.com on Fri, Sep 29, 2000 at 07:28:54AM -0400 References: <20000929013521.C27736@fw.wintelcom.net> <Pine.SUN.3.91.1000929072626.7930A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Daniel Eischen <eischen@vigrid.com> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000929103756.I27736>