From owner-freebsd-threads@FreeBSD.ORG  Mon Jul 14 05:53:08 2003
Return-Path: <owner-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 1059537B401
	for <freebsd-threads@freebsd.org>;
	Mon, 14 Jul 2003 05:53:08 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 237DF43F93
	for <freebsd-threads@freebsd.org>;
	Mon, 14 Jul 2003 05:51:47 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h6ECpkAI021047;
	Mon, 14 Jul 2003 08:51:46 -0400 (EDT)
Date: Mon, 14 Jul 2003 08:51:46 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Kai Mosebach <kai.mosebach@freshx.de>
In-Reply-To: <000601c349f9$39b69fe0$0100000a@alpha>
Message-ID: <Pine.GSO.4.10.10307140841530.19808-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-threads@freebsd.org
Subject: Re: AW: getpwnam + getpwnam_r + LinuxThreads port = deadlock
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: deischen@freebsd.org
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 12:53:08 -0000

On Mon, 14 Jul 2003, Kai Mosebach wrote:
> > On Sat, 12 Jul 2003, Joshua Oreman wrote:
> > 
> > > >
> > > >   3) CVSup to the latest 5.x and use libthr or libkse and
> > > >      forget linuxthreads.
> > >
> 
> I am having the same problems in my sapdb port, as mentioned in another
> mail. For me its also not this simple to simply switch to kse, because
> then
> other kse related problems occur.

Like what?  The -threads list is a good place to post these
problems.

> Wouldnt it be more "clean", to fix the issue in the linuxthreads
> implementation instead ? (For example many users might use linuxthreads
> for mysql compilation for example, not knowing what they await ...)

Have you tried sending the problem to the maintainer?
Our main concern is libthr and libkse stability for
5.2-release.  Eventually the ports system will learn
about our other thread libraries and will allow their
use in preference to linuxthreads.

-- 
Dan Eischen