From owner-freebsd-threads@FreeBSD.ORG Tue Apr 18 21:51:28 2006 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D272516A401 for ; Tue, 18 Apr 2006 21:51:28 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2475643D45 for ; Tue, 18 Apr 2006 21:51:28 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k3ILpRsC024424; Tue, 18 Apr 2006 17:51:27 -0400 (EDT) Date: Tue, 18 Apr 2006 17:51:27 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Maxim Konovalov In-Reply-To: <20060419014445.I73773@mp2.macomnet.net> Message-ID: References: <200604182133.k3ILXmZp085715@freefall.freebsd.org> <20060419014445.I73773@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-threads@freebsd.org 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 Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 21:51:28 -0000 On Wed, 19 Apr 2006, Maxim Konovalov wrote: > On Tue, 18 Apr 2006, 17:43-0400, Daniel Eischen wrote: > >> On Tue, 18 Apr 2006, Maxim Konovalov wrote: >> >>> Synopsis: libc_r does not honor socket timeouts >>> >>> State-Changed-From-To: open->closed >>> State-Changed-By: maxim >>> State-Changed-When: Tue Apr 18 21:33:23 UTC 2006 >>> State-Changed-Why: >>> Superseded by threads/24472. >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=20861 >> >> And I'll close threads/24472 because it has been superceded by >> libpthread and libthr unless you have other plans for it. > > 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 :-) -- DE