From owner-freebsd-threads@FreeBSD.ORG Tue Mar 16 10:20:10 2004 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98FF716A4D0 for ; Tue, 16 Mar 2004 10:20:10 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E6BE43D31 for ; Tue, 16 Mar 2004 10:20:10 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i2GIKAbv037166 for ; Tue, 16 Mar 2004 10:20:10 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i2GIKAO5037165; Tue, 16 Mar 2004 10:20:10 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Mar 2004 10:20:10 -0800 (PST) Message-Id: <200403161820.i2GIKAO5037165@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Craig Rodrigues Subject: Re: kern/64313: FreeBSD (OpenBSD) pthread implicit set/unset O_NONBLOCK flag X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Craig Rodrigues List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2004 18:20:10 -0000 The following reply was made to PR kern/64313; it has been noted by GNATS. From: Craig Rodrigues To: freebsd-gnats-submit@FreeBSD.org Cc: lars@koellers.net Subject: Re: kern/64313: FreeBSD (OpenBSD) pthread implicit set/unset O_NONBLOCK flag Date: Tue, 16 Mar 2004 13:10:53 -0500 Hi, What is the point of this PR? It contains a patch to what looks like a program in ports. The O_NONBLOCK issue with libc_r is known. Take a look at: http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/41331 This problem doesn't occur with the new KSE ( http://www.freebsd.org/kse ) libpthread implementation of threads in FreeBSD 5.x. Most likely this problem will not be fixed in libc_r, since most efforts these days are focused on getting libpthread solid in 5.x. Dan Eischen has been suspending (and not closing) these kinds of PR's, i.e. problems that occur in libc_r but not in libpthread, because most likely they will not be fixed in libc_r (but they may be one day, if someone takes an interest in fixing up libc_r).