From owner-freebsd-threads@FreeBSD.ORG Tue Apr 18 23:14:22 2006 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D0FCC16A403; Tue, 18 Apr 2006 23:14:21 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-threads@freebsd.org Date: Wed, 19 Apr 2006 07:14:15 +0800 User-Agent: KMail/1.8.2 References: <200604182133.k3ILXmZp085715@freefall.freebsd.org> <20060419015433.S73773@mp2.macomnet.net> In-Reply-To: <20060419015433.S73773@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604190714.15447.davidxu@freebsd.org> Cc: Daniel Eischen Subject: Re: kern/20861: libc_r does not honor socket timeouts X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 23:14:22 -0000 On Wednesday 19 April 2006 05:55, Maxim Konovalov wrote: > [...] > > > > Yep, I wonder about libc_r PRs state. We need to decide actually what > > > and when we are going to do with them. Kill them all right now? > > > > I'd vote for that :-) > > If I don't hear any objections by Friday I'll close them. > > Thanks, Dan! This PR is also not true for libthr both in 6.x and -HEAD: threads/76690threads =A0 =A0 fork hang in child for (-lc_r & -lthr) David Xu